HAPI FHIR Server Configuration

The HAPI FHIR Server image has its own application.yaml. Values in .hapi.env override selected properties from that YAML file without modifying the image.

[!NOTE] The upstream configuration is src/main/resources/application.yaml in the official HAPI FHIR JPA Server Starter repository. The master branch may differ from the healthtag/hapi-fhir-jpaserver image, so compare against the source or tag used to build the deployed image. The dotted environment-variable names below follow the same property paths as the YAML.

FHIR Browser address

HAPI includes a web-based FHIR Browser. hapi.fhir.tester.home.server_address tells that browser which FHIR base URL to call. The URL is used by the user’s web browser, not by the HAPI container, so it must be reachable from the user’s machine.

Set it to an internal address such as http://<INTERNAL_NODE_IP>:8080/fhir, or to the protected internal gateway URL used by the hospital. Do not set it to a Docker-only hostname such as hapi-fhir-jpaserver-start, because a browser outside the Docker network cannot resolve that name.

[!WARNING] The included FHIR Browser can create, read, update, and delete FHIR data. It is an administrative testing tool, not a public interface. Keep both the browser and its configured server address on an internal network with appropriate access controls.

Environment variables

The repository sets all three variables below. Check them against the HAPI image version selected for the installation.

Variable	Default Value	Explanation
hapi.fhir.tester.home.server_address	(empty)	FHIR base URL used by the included FHIR Browser. Set an internal URL that is reachable from each administrator’s machine.
hapi.fhir.tester.home.fhir_version	R4B	FHIR version used by the FHIR Browser in this repository.
hapi.fhir.fhir_version	R4B	FHIR version processed by the HAPI JPA Server in this repository.