Application vendors can access the eHealth infrastructure services through using the service URLs as listed for each environment Environments.
The external URLs follow the pattern:
https://{service}.{environment}.ehealth.sundhed.dk/{path}
Eg., to get metadata from the task service in exttest environment:
https://task.exttest.ehealth.sundhed.dk/fhir/metadata
But when developing a service that is deployed inside the Kubernetes cluster in the namespace assigned to a vendor, then the service must use the cluster internal URLs to access the eHealth infrastructure services.
The eHealth infrastructure services are deployed in the ehealth-public namespace, and for a service deployed in a vendor namespace, the access to a service in the ehealth-public namespace must use the cluster internal URL pattern:
http://{service}.ehealth-public/{path}
Eg., for a vendor service deployed in the exttest environment, to get metadata from the task service:
http://task.ehealth-public/fhir/metadata