Environments

The PPS API is offered in several environments, primarily two of which are relevant for external API consumers: Test and Prod.

The test environment is available on the internet, while Prod is only available on the health network. Therefore, it is a requirement that your organization has membership in the health network to consume the API.

Below is an overview of available environments, as well as which DNS they are available on.

Note: We are in the process of moving our services to new environments. The second url is the one to be used in the new environments. Consumers can swithch to the new environment at will and will be contacted before the old ones gets terminated. Beware that the new environments run refactored implementations of the services and minor differences may be relevant.

Environment Base-Url - to be phased out New Base-Url Availability (DNS)
Test https://test.nilar.nhn.no https://test.pps.nhn.no Internet, Health network
Prod https://prod.nilar.nhn.no https://pps.nhn.no Health network

Test

  • Prod-like test environment, available for internal and external use,
  • Main test environment for cross-environment testing in NHN and for externals.
  • Used for functional testing of integration from professional systems against the service.
  • No dependencies on other services.
  • We do not want the environment to be used for performance testing unless it has been agreed upon in advance.
  • For syntetic test data only! No real data containing personal or person identifying data should exist in this environment.

Note: This environment is widely available and must not contain sensitive information of any kind. It is the responsibility of producers into this environment to ensure that data is properly synthesized, using synthetic person identifiers etc.

Prod

  • Production environment.
  • Production should never, under any circumstances, be used for testing neither on synthetic nor real persons.

Please note that all new services made available from NHN's private cloud are published on a different IP segment than some other NHN services. If your organization already uses services via the health network, you may need to add new firewall rules for NHN private cloud.