Frequently Asked Questions

Becoming a partner

1. How do I become a partner?

Go to to read about our partner packages. Fill out our contact form to get in touch with us.

2. How do I register my team for API access after becoming a partner?

Send a list of your team's email adresses to, and we will grant them the necessary API access after a contract has been signed. Ensure that all your team members have created an Open DIPS account prior to sending the list.

3. What happens when my contract ends?

When your contract ends, you will be set back to the Basic partner package.


1. What is the difference between OpenID Connect and Open DIPS login?

Your Open DIPS account is used to manage the APIs you have access to and interact with our developer portal. When interacting with Arena or the APIs outside the developer portal, you will need credentials for the DIPS Federation Service.

2. Can I use a third-party Identity Provider within DIPS APIs?

We can configure our APIs to trust any identity provider that follows OAuth, e.g. Microsoft Entra ID. This is something we can set up on a case-by-case basis that requires a partner package in DIPS.

3. What types of integrations do the APIs in DIPS Arena support?

You can integrate with our APIs from regular applications where users log in with their DIPS credentials (using the Authroization Code Flow) or through a system integration (using Client Credentials Flow). There is also an option to run a web-application within the DIPS Arena client by utilizing SMART on FHIR. This can utilize Single-Sign On, and users have easy access to your application.

4. I am getting the error "unauthorized_client" on the client Credential flow. Is there something wrong with my credentials?

There are multiple scenarios in which you might get 'unauthorized_client'. This may happen when the client id/secrets are wrong, the redirect uri is not correct, or you have tried to request an authorization scope that has not been added for your client. Double check that the information you have is correct. Please contact us at if this does not resolve the issue.

Virtual test-hospital and synthetic patient data

1. What do you mean by synthetic data?

Synthetic data in Open DIPS refers to artificially generated healthcare information that mimics real patient data while ensuring the privacy and confidentiality of individuals. This approach involves creating fictitious but realistic patient records, medical histories, and health-related data to simulate the characteristics of authentic datasets.

2. Is it possible to create a new practitioner role and organization for demoing purposes?

We recommend using existing synthetic data for demoing purposes. Practitioner roles are configured by the hospital administration, and it is not configured for applications specifically. Our access control is based on permissions assigned to a given practitioner role. The organizational structure is also configured by the hospital administration. It is not guaranteed that external organizations are added to their database.

3. What kind of data is available in the test environment?

We have a variety of test data in the Open DIPS environment, including some of the standard test actors from Norsk Helsenett like Roland Gundersen and Line Danser. Learn about the test patients here.

4. Is it possible for me to create data in the test environment?

Yes, it is feasible to manually generate certain data within the test environment, such as patient information by using the FHIR Patient API. Nevertheless, we are currently investigating an innovative approach to tailor test data according to your specific requirements. For further details on this matter, we invite you to visit Synne.

DIPS and the Norwegian healthcare system

1. What is DIPS Arena?

DIPS Arena is a comprehensive electronic health record (EHR) system used in the Norwegian healthcare system. Developed by DIPS ASA, a Norwegian health informatics company, DIPS Arena is designed to digitize and streamline various aspects of healthcare management, including patient records, clinical workflows, and administrative processes.

Key features of DIPS Arena include:

  1. Patient Records: The system maintains electronic health records for patients, consolidating information such as medical history, diagnoses, medications, test results, and treatment plans in a digital format.
  2. Clinical Workflows: DIPS Arena supports healthcare professionals in managing clinical workflows efficiently. It includes tools for order entry, results reporting, and decision support to enhance the delivery of patient care.
  3. Integration: DIPS Arena is designed to integrate with various healthcare systems and technologies, allowing seamless communication and data exchange between different components of the healthcare infrastructure.
  4. Decision Support: The system provides decision support features to assist healthcare providers in making informed and evidence-based decisions about patient care.
  5. Administrative Functions: DIPS Arena includes administrative tools for tasks such as scheduling, billing, and resource management, contributing to the overall efficiency of healthcare operations.
  6. Security and Privacy: Given the sensitive nature of health information, DIPS Arena incorporates robust security measures to protect patient data and ensure compliance with privacy regulations.

DIPS Arena plays a crucial role in modernizing healthcare delivery in Norway by promoting the use of digital technologies to enhance patient care, improve efficiency, and facilitate collaboration among healthcare professionals. The system is used in hospitals and healthcare institutions across the country to support a more integrated and data-driven approach to healthcare management.

FHIR and DIPS Arena

1. What is SMART on FHIR?

SMART on FHIR (Substitutable Medical Applications, Reusable Technologies on Fast Healthcare Interoperability Resources) is an innovative framework that integrates apps with electronic health records (EHRs) across different healthcare IT systems. It's a set of open standards and protocols designed to enable developers to create interoperable healthcare applications. The "SMART" part enables apps to be easily added or removed from an EHR system (like smartphone apps), and "FHIR" (pronounced "fire") is a standard for exchanging healthcare information electronically. Together, they support the development of applications that can securely and seamlessly access and use data from EHRs, enhancing the potential for personalized medical care and streamlined healthcare processes.

2. How does SMART on FHIR work in DIPS Arena?

In DIPS Arena we have support for adding SMART on FHIR applications to the client. This means that you can run your application within the DIPS Arena client, and have access to the patient context and other relevant information from the EHR. This is done by using the SMART on FHIR protocol.

3. How can I get access to SMART on FHIR in DIPS Arena?

To get access to SMART on FHIR in DIPS Arena, you need to be a partner. You can read more about our partner packages here. If you are already a partner, you can contact us at

Did you find what you were looking for?

We use cookies to enhance your experience.
For a complete overview of all cookies used, please see our privacy policy.

DIPS ASPostboks 1435, 8037 BodøTlf: +47 75 59 20 00open@dips.no20240415.2