Environments and Base URLs

Environments

The Pasientens Rekvisisjoner API is available to external API consumers in two separate environments:

• Test: Only for test data regarding synthetic patients
• Production (or Prod): Only for real data regarding real patients

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.

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.
• We do not want the environment to be used for performance testing unless it has been agreed upon in advance.
• For synthetic test data only! No real data containing personal or personally identifiable 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.

Production/Prod

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

Note: 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.

Base URLs

Below is an overview of available base URLs in the two environments, as well as which DNS they are available on.

To get familiar with the API the concept of backdoor endpoints are available. These are endpoints that bypass authentication in Test and can be used in startup and early development phases, but do not use the same header naming as the authenticated endpoints.

* Backdoor endpoint that uses internal headers instead of the headers used by the other endpoints.