The joint testing process

The joint testing process is divided into a phase of independent testing by the information system supplier and a phase of joint testing.

Before joint testing

Ensure that the information system meets national requirements. The information system must be based on key requirements and information system profiles in accordance with national regulations and THL regulations.

The development of information systems is governed nationally by

The Kanta Services’ publication schedule includes timetables for the development of functionalities and deadlines for deployment in the social and health sectors. The publication schedule also shows the timelines for joint testing readiness.

Please also see the service-specific joint testing content.

To join the client test service, please submit an application to join the relevant Kanta service. Joining requires an information system that meets the use cases and requirements of the service you are applying for. The system supplier always connects to the Kanta client test environment from its own test environment. Applications are processed within three weeks.

To use the client test service, you need social and healthcare test cards (dvv.fi)(opens new window)and test service certificates (dvv.fi)(opens new window) (server and system certificates). These are ordered from the Digital and Population Data Services Agency.

Joining the Kanta PHR client test environment and registering for joint testing can be done simultaneously using the application to join. Prior to this, application developers carry out independent testing in a sandbox environment. Further information on the sandbox environment.

For more detailed instructions, please see the “Ohjeet” tab of the application to join (in Finnish):

For information on Kanta client test environments, please see the Test Environments page.

Comprehensively test all defined functionalities in the client test environment of the Kanta client test service, and ensure that the information system meets the requirements of the specifications.

Validate documents stored in Kanta in the validation service.

Be sure to apply for the necessary access rights well in advance. Our Kanta testing experts will tell you whether you need access to the Testain service, the Kumppanit workspace, or both. The new Testain service for joint testing will be introduced in phases from spring 2025, and will continue to run in parallel with the Kumppanit workspace for joint testing for the time being.

Testain service for joint testing

Testain is a service that facilitates joint testing. Testain will be deployed in phases from spring 2025.

Kanta’s joint testing Testain service streamlines the joint testing process and facilitates the monitoring of the information system supplier's situation and communication during ongoing joint testing. Joint testing will be moved to Testain in phases. More detailed information can be found on the Testain page.

Log in to Testain using suomi.fi credentials. The information system supplier must authorise service users itself. More information on suomi.fi credentials can be obtained from the Digital and Population Data Services Agency(opens new window). 

Joint testing in the Kumppanit workspace

Each system supplier has its own Kanta service-specific Kumppanit workspace (SharePoint), which is only accessible by representatives of that system supplier and representatives of their client organisations. Access rights are verified at the start of joint testing.

In the transition phase, the Kumppanit workspace will serve alongside Testain as a communication channel for the system supplier, its client organisation, and the Kanta Services. Test cases are also reported in the Kumppanit workspace until the testing in question is entirely transferred to Testain.

The Kanta Services store documents related to joint testing in the system-specific Kumppanit workspace, such as:

  • registration forms
  • test personal identification numbers used for joint testing
  • joint testing test cases
  • audit findings
  • style files for statements and certificates to be stored in the Patient Data Repository.

Kumppanit workspaces:

First test your information system against the Kanta Services by carrying out preliminary tests. Preliminary test cases ensure that the information system is ready for joint testing. The preliminary test cases are carried out with an implementation that complies with the Kanta specifications. 

If no significant errors are found, testing between the system supplier and Kela will proceed. The preliminary test cases are described in the registration form for each joint test.

Joint testing preliminary tests will be migrated to Testain in phases and a separate registration form will no longer be necessary for the tests that are in Testain.

Report the pre-defined preliminary test cases for the test in question. These can be found on the registration form or requested from Kela. If the purpose of the system so requires, Kela can tailor the content and scope of the preliminary test cases on the registration form if necessary. The number of preliminary test cases varies depending on the content being tested. 

During joint testing

Register for joint testing for the content of the Kanta Service in question. If preliminary test cases have been reported in the Testain service, registration for joint testing will also take place in Testain.

For more detailed information, please see the Registering for joint testing page. 

When registering, a THL system form must be submitted to Kela (THL Regulation 5/2024, Appendix 4). Remember to accurately indicate the information system profiles according to the purpose of the system (THL regulation 5/2024) and the purpose of the system itself. Kela may also request an architecture description if necessary. 

The system form is a key document for the joint testing of Kanta Services, as it (and the information system profiles indicated in the system form) define the content and scope of the joint testing required for the information system.

If necessary, Kela can tailor the content and scope of the joint testing based on e.g. the purpose of the information system. The number of test cases varies according to the content to be tested.

Kela will review the preliminary test cases and, if anything is found that needs correcting, the information system supplier will be asked to correct the shortcomings and report the preliminary test cases again.

When there is no longer anything to be corrected in pretest cases, a joint testing expert will provide the actual test cases to be performed. If necessary, Kela will organise a separate initial meeting for joint testing.

Carry out the actual test cases as instructed by your joint testing expert.

The testing between the information system supplier and Kela examines the functioning between the information system or wellbeing application to be connected to the Kanta Services and the Kanta Services. In particular, the messages to be stored and their structure will be tested.

This testing phase is typically performed in the system or application supplier's own test environment, which is connected to the Kanta Services' client test environment. In some situations, however, the client organisation’s test environment may be the only test environment where joint testing can be performed. Such a situation can arise when testing modular information system packages or the Imaging Data Repository, for example.

During the transition phase, the joint testing expert will tell the system supplier whether to report test cases in the Kumppanit workspace or the Testain service. If the Kanta Services detect errors in the test cases, the system supplier will correct the errors and demonstrate the functionality of the corrections through retesting.

Kela will tell you if there is a need for testing between the client and Kela

The initial meeting will discuss the testing phases of joint testing and whether joint testing will include testing between the client organisation and Kela. This is usually only necessary in the largest cases. 

In this case, testing is carried out in a test environment belonging to the system supplier’s client, such as a wellbeing services county. The client’s test environment is connected to the Kanta client test environment.

The purpose of cross-testing is to ensure that the documents archived in the Kanta Services are interoperable between various information systems. Cross-testing is not required for all test contents.

If cross-testing is required, the Kanta Services will search for partners for cross-testing and provide test cases. System suppliers are responsible for any testing costs they accrue.

System suppliers’ client organisations cross-test test cases in the client organisation's test environment, which is connected to the Kanta Services’ client test environment. Information system suppliers from each party will participate and support the client organisation in the testing. Ongoing joint testing is not required for both parties to a cross-test.

If the system is in production, it is required by law to participate in joint testing to ensure interoperability between information systems (Section 86 of the Client Data Act (finlex.fi)(opens new window)).

After joint testing

Once joint testing has been successfully completed, Kela will issue a joint testing statement for the information system. A more detailed joint testing report is attached to the statement.

Kela also sends the joint testing statement and report to the Finnish Institute for Health and Welfare (THL), Valvira, and the information security inspection body for information.

The information system supplier must inform Valvira when the system receives a new joint testing report.

Registration of information systems (valvira.fi)(opens new window).
 

Before starting production use, verify if a deployment test is required.

Deployment test practices vary from one Kanta service to another. You can find more detailed information at From testing to production. 

Report any changes to a system that is connected to Kanta.

Kanta must always be informed of any changes to a system connected to Kanta’s Prescription Service, Patient Data Repository, the Client Data Repository for Social Welfare Services, and of any changes to the system’s functionalities or interface. Changes to Wellbeing applications that have joined Kanta must also be reported to Kela.

Kela will assess the need for joint testing based on the notice of change. Joint testing is not always required, and sometimes it can be very limited in scope.

Obligation to provide notice of changes.