Clinicom Server

The Clinicom Server communication point enables messages to be exchanged with the Clinicom Patient Management System.

Supported Operational Modes: Input, Output.

In order to make this server communication point more tolerant to connection failures from clients or misconfigured clients, it is recommended that its connection retry count be set to infinite. Refer to Connection Retries for details.

Input Mode Properties

Property	Description
Local Port	The local port to which you want bind the connection.
Local Address	The local interface to which you want to bind the connection.
Listen Backlog	The number of connections that can be waiting for a connection before others are refused. The backlog specified must be greater than zero.
Use SSL	Options: `True`, `False`. Default: `False`. If `True`, secure socket layer is used for this connection and all messages are encrypted. Refer to TLS/SSL Support in Rhapsody for details on TLS/SSL (Transport Layer Security/Secure Sockets Layer) support in Rhapsody. It is strongly recommended that SSL be enabled for Clinicom Server communication points.
SSL Protocol Mode	Refer to SSL Protocol Versions for details.
SSL Cipher Suites	Refer to SSL Cipher Suites for details.
Use SSL Client Mode	Options: `True`, `False`. Default: `False` If `True`, SSL client mode will be enabled. Note that this is NOT the same as enabling client authentication: TLS client authentication is enabled by configuring one or more trusted certificates for the connection.
Secure Keys	The list of private keys to choose from when selecting a private key to use in the communication with the client. If the Secure Keys configuration property is not configured with the SSL server's private key, then this SSL server operates in anonymous server authentication mode, and so enables the appropriate anonymous cipher suites. However, it is highly recommended that the server's private key always be provided here to allow server authentication to be performed. If the server does not have a private key, then one can be generated from Rhapsody's certificate manager. Refer to Server Authentication for details.
Trusted Certificates	Identifies the trusted certificates used at the non-Rhapsody end of the SSL connection. If it is configured with one or more certificates, then the SSL server requires client authentication as part of the SSL protocol negotiation, and will reject clients that do not present either the configured certificate, or a certificate directly or indirectly issued by the configured certificate. It is highly recommended that client authentication be enabled whenever possible. Refer to Client Authentication for details.
Output Debug Info	Options: `True`, `False`. Default: `False` If the debug information should be output to the Rhapsody log.
Include DAT Header	Options: `True`, `False`. Default: `True` If the messages (both those received and to be sent) should include the DAT header.
Block Separator	If non-empty received blocks will be searched for a terminating separator which, if found, will be stripped. Sent blocks will have the separator added.
Log Connections	Log the establishing and dropping of all connections.
Log Data	Options: `True`, `False`. Default: `False` Log all data sent and received by this communication point to a file.
Log Data as Hex	Options: `True`, `False`. Default: `False` Write all logged data to the log as hexadecimal.
Connection Log File	The file to log the connection information to.
Extra Information	Options: `Log Time`, `None`. Default: `Log Time` Timestamps will be written with each event.
Sequence Number Property Name	The name of a property to populate with a sequence ID.

Output Mode Properties

Property	Description
Local Port	The local port to which you want to bind the connection.
Local Address	The local interface to which you want to bind the connection
Listen Backlog	The number of connections that can be waiting for a connection before others are refused. The backlog specified must be greater than zero.
Use SSL	Options: `True`, `False`. Default: `False` If `True`, secure socket layer will be used for this connection and all messages will be encrypted. Refer to TLS/SSL Support in Rhapsody for details on TLS/SSL (Transport Layer Security/Secure Sockets Layer) support in Rhapsody. It is strongly recommended that SSL be enabled for Clinicom Server communication points.
SSL Protocol Mode	Refer to SSL Protocol Versions for details.
SSL Cipher Suites	Refer to SSL Cipher Suites for details.
Use SSL Client Mode	Options: `True`, `False`. Default: `False` If `True`, SSL client mode will be enabled. Note that this is NOT the same as enabling client authentication: TLS client authentication is enabled by configuring one or more trusted certificates for the connection.
Secure Keys	The list of private keys to choose from when selecting a private key to use in the communication with the client. If the Secure Keys configuration property is not configured with the SSL server's private key, then this SSL server operates in anonymous server authentication mode, and so enables the appropriate anonymous cipher suites. However, it is highly recommended that the server's private key always be provided here to allow server authentication to be performed. If the server does not have a private key, then one can be generated from Rhapsody's certificate manager. Refer to Server Authentication for details.
Trusted Certificates	Identifies the trusted certificates used at the non-Rhapsody end of the SSL connection. If it is configured with one or more certificates, then the SSL server requires client authentication as part of the SSL protocol negotiation, and will reject clients that do not present either the configured certificate, or a certificate directly or indirectly issued by the configured certificate. It is highly recommended that client authentication be enabled whenever possible. Refer to Client Authentication for details.
Output Debug Info	Options: `True`, `False`. Default: `False` If the debug information should be output to the Rhapsody log.
Include DAT Header	Options: `True`, `False`. Default: `True` If the messages (both those received and to be sent) should include the DAT header.
Block Separator	If non-empty received blocks will be searched for a terminating separator which, if found, will be stripped. Sent blocks will have the separator added.
Log Connections	Log the establishing and dropping of all connections.
Log Data	Options: `True`, `False`. Default: `False` Log all data sent and received by this communication point to a file.
Log Data As Hex	Options: `True`, `False`. Default: `False` Write all logged data to the log as hexadecimal.
Connection Log File	The file to log the connection information to.
Extra Information	Options: `Log Time`, `None`. Default: `Log Time` Timestamps will be written with each event.
Enforce 256 maximum block size	Options: `True`, `False`. Default: `False` If true, message blocks bigger than 256 bytes are split into multiple blocks when sent.