Kanta Services issues a statement to the information system provider on successfully completed joint testing. The Kanta Services also sends information about successfully completed joint testing to the National Institute for Health and Welfare (THL), Traficom and Valvira.
Joint testing is required in different situations
Joint testing may be required in different situations:
- certification of a new information system
- legislative amendments
- change in the definitions of the Kanta Services
- significant system change (provider-initiated change in the system)
- changes to the classification of the system.
Certification of a new information system
After the joint testing, an information security assessment of the information system is carried out and a certificate of the completed information security assessment is written for the system. The information system supplier provider submits the joint testing statement required for the assessment to the data security assessment body.
The information system provider submits a register notification to Valvira, which adds the information system in question to Valvira's information system register. The introduction of the new system in customer organisations requires a deployment test, and it can only be proceeded with once the information security assessment has been completed and Valvira has registered the information system.
Legislative amendments and change in the specifications of the Kanta Services
Functionality that is jointly tested based on a legislative amendment must be in production use by the customer organisation within the time limit specified by law.
Jointly tested functionality or data content based on a change to specifications of the Kanta Services will be taken into production use within a separately defined time limit, e.g. as stated in the release schedule.
In some situations, a deployment test may be required for the transition to production use. Check whether a deployment test is required in the instructions for the extension of use or contact kanta@kanta.fi.
Significant system change
Functionality or information content tested due to a system change made by a system provider shall be taken into production use within the time limit specified by the provider.
In some situations, a deployment test may be required for the transition to production use. Check whether a deployment test is required in the instructions for the extension of use or contact kanta@kanta.fi.
Changes to the classification of the system
The transition to production use requires a separate deployment test if the classification of the system rises to class A2 or A3.
Pre-production deployment testing
The system provider conducts a deployment test with the customer organisation. The purpose of the deployment test is to technically verify that the Kanta connection between information systems works.
- deploying a completely new system
- the classification of the system changes to class A2 or A3
- legislative amendments or changes in the specifications of the Kanta Services
- significant system change (provider-initiated change in the system)
Deployment test in the Patient Data Repository and the Social Welfare Customer Data Repository
The deployment test shall be conducted in accordance with or by applying a test case prepared for the deployment test. The customer organisation or system provider that conducted the deployment test shall send a report of the successful deployment test to Kela within two working days of the completion of the test.
Production use of the system can be started immediately after a successful deployment test. More detailed descriptions of deployment phases, test cases and the reporting template for the deployment test can be found on the service deployment and service extension pages.
Deployment test in the Prescription Service and the Archive of Imaging Data
In the Prescription Services and the Archive of Imaging Data, the system provider agrees on the deployment test with Kela by sending a message to kanta@kanta.fi.