FHIR Service

With this service, you can establish a connection to a target FHIR server and share the connection among the XEServer FHIR components to perform operations on FHIR resources.

Tip Alternatively, each individual XEServer FHIR component can use its own connection settings.

Connection Tab

On this tab, you can specify connection parameters to connect to a target FHIR server. For more information, see FHIR connection parameters.

SSL Tab

On this tab, you can configure the connection security parameters.

Warning DSA certificates are not supported as a result of migration to Java 11. For SSL connections, you have to use RSA certificates instead.

Field	Description
Use default Java trust store	Select this option to get trust store certificates from the currently used Java installation when establishing the SSL connection.
Enable hostname validation	Select this option to ensure security by validating the host name.
Trusted store
Path	Specify the path to the key store with trusted certificates.
Truststore Password	Specify the password to the key store with trusted certificates.
Key store (required for SSL with client authentication)
Path	Specify the path to the file which contains key store certificates.
Keystore Password	Specify the password to the file which contains key store certificates.
Key password	Specify the password to the private key.

Proxy Tab

On this tab, you can configure HTTP(S) proxying for the service. The following proxy settings are available:

Field	Description
Use Proxy Server	Select this option to enable the Proxy Server.
Host	The IP address or the host name of the proxy server to be used.
Port	The port number to be used for the connection.
Authorization	The authorization type to be used when connecting to the proxy server. The following options are available: None: No authorization is performed on the proxy server. Basic: A basic authorization type is used (Base64-encoded name and password). Digest: A more complex authorization type (plain text user name and a hashed password). NTLM: A Windows-specific authorization type based on Windows user name and a password. Note For the NTLM authorization type, the user name must contain a domain name, for example: someDomain\Administrator.

Authorization Tab

On this tab, you can specify how the target FHIR server should authorize the XEServer's connection. For more information, see FHIR authorization parameters.

Dependencies Tab

On this tab, you can view the route components associated with the current service. Click a component to view the component in the Route Editor.