|System Name||The name of this system. It is shown on all web pages served up by HL7Connect, and also identifies this instance of HL7Connect on any notification messages sent by HL7Connect. The default value is simply "HL7Connect". It is useful to set an appropriate name if you get notifications from more than one HL7Connect.|
|Test System||Mark this HL7Connect as a test or development installation. The only difference this makes is that the HL7Connect web pages are clearly marked as "Test System". By default, HL7Connect is not marked as a test system.|
|Telnet Server Port||The default Telnet server port is 23456. This can be changed to any port not already in use. Restarting HL7Connect is necessary for changes to the Telnet port to become effective. You can telnet to the specified port here to access the "back-end" of HL7Connect and see in real time the messages being processed.|
The IP address, or network name, of the SMTP server used by HL7Connect when sending email.
Interfaces can send email to a nominated user when certain circumstances occur.
The normal port for SMTP is 25. If you need to specify a different port, you can append it to the address with a colon, like this: 127.0.0.1:10023.
The email server must be configured to relay email for the combination of sender's email and IP address, and the destination email address. NOTE: Contact your network administrator for further details of this procedure.
|Ignore SMTP Errors||Checking this option allows HL7Connect to continue operating if any SMTP errors are encountered|
|SMTP UserName||Some SMTP hosts require user authentication to allow an email to be sent. A user account can be specified via this option.|
|SMTP Password||Some SMTP hosts require user authentication to allow an email to be sent. The password for a user account can be specified via this option.|
|HL7Connect Email Address||This email address is used as the "Sender" address when HL7Connect generates an email. Generally, this email address does not need to exist, however on some email systems this must correspond to a real user in order for the mail server to accept the email.|
|Interface Audit Storage Period||
Sets the number of days the interface audit logs will be stored in the database. The default is 60 days - log entries older than 60 days are cleared daily. Setting the storage period to zero allows a log to be kept indefinitely.
The Interface Audit Trail includes a record of all events associated with the interface, including system start and stop events, interface start and stop events, transport layer start and stop events, and an audit trail for interface reconfiguration.
Events that are user-driven, such as starting / stopping / reconfiguring an interface are not removed with the log, but are kept indefinitely. You can remove the log completely through the Browse Logs page.
|Message Storage Period||
Dictates how long messages are kept in the HL7Connect messages store if the storage settings on an interface level aren't specified. You can also choose to archive these messages for deletion rather than delete them by ticking the "Archive before deleting" option.
When enabled, order messages in forwards order (chronologically) by default when browsing messages. If this is not selected then the default order is in reverse order so that the most recent messages are shown first.
|Night Time Notification Period||
The interfaces can be configured to provide a notification if no messages are received within a given period of time. The time can be configured differently for day time and night time. This setting configures the time of day that is considered to be night time. By default, night time is 21:00 to 07:00. Evening must come after morning, and day time is the period between the two times.
|HL7 v2 Compression||
By default, HL7 v2 messages are compressed in the message store, using ZLib compression. The compression can be turned off using this flag. This might be done because the compression is slowing processing time (particularly where the messages are large and contain already compressed image data). Alternately, direct access to the messages in the database might be desired, this is not recommended.
By default, CDA Documents are compressed in the message store, using ZLib compression. The compression can be turned off using this flag. This might be done because the compression is slowing processing time (though generally CDA documents are large and highly compressible). Alternately, direct access to the documents in the database might be desired, this is not recommended.