Deployment & Configuration

Deployment options

The XDS-registry-to-fhir app is packaged as a single jar, containing a Tomcat runtime. To simplify the whole setup, the app is packaged with a JAVA runtime in a docker container and published to: https://hub.docker.com/r/thopap/xds-registry-to-fhir

Application configuration properties

The following application properties can be used to adjust the application behavior by setting them either in a application.properties or by setting the corresponding environment variable.

Property Name (Environment Variable)	Description	Default
fhir.server.base (FHIR_SERVER_BASE)	Endpoint of the FHIR R4 Server that will be used as backend	http://hapi.fhir.org/baseR4
server.port (SERVER_PORT)	Server HTTP port.	8081
xds.defaultHash (XDS_DEFAULT_HASH)	In case the FHIR DocumentReference do not has a hash, use this as default when mapping to XDS. For documents registered by this implementation, this should never be the case.	0000000000000000000000000000000000000000
fhir.server.profile.bootstrap (FHIR_SERVER_PROFILE_BOOTSTRAP)	If true, server will upload MHD relevant resources (StructureDefinition) to the FHIR server to allow validation.	false
xds.repositoryEndpoint. (XDS_REPOSITORY_ENDPOINT_<OID_with_underscore>)	For each connected XDS Repository, there must be a configuration which Map the repsitory OID to a http Endpoint pattern, where some remote client can get the binary content. The URL should contain a placeholder $documentUniqueId which will be filled by this xds-fhir server.	http://gazelle/binary2/$documentUniqueId
xds.unknownRepositoryId XDS_UNKNOWN_REPOSITORY_ID	In case the FHIR DocumentReference contain a http endpoint that can not be mapped to on of the configured repostories, use this a fallback.	2.999.1.2.3