The preparations include independent testing by the information system supplier in its own test environment and against the client test service. In joint testing, the preliminary test cases of the Kanta services are carried out.
Joint testing process for information system suppliers
Different phases of the joint testing process are presented in the graph (in Finnish only).
The information system supplier registers for the joint testing in terms of each content to be tested. In connection with registration, the supplier must report pre-defined preliminary test cases, which are found on the registration form or sent from Kela on request. When the preliminary test cases have been successfully performed, Kela will hold a kick-off meeting with the supplier where the details related to joint testing are discussed. Depending on the contents to be tested, there are between one and three testing phases in joint testing. When all testing phases have been successfully passed, Kela will issue a joint testing statement and report for the information system. If any changes are made to the contents that have undergone joint testing, they must be notified to Kela on the notice of change.
Duration of joint testing
Every Kanta service has its own joint testing period, and its more detailed contents and timetable are planned separately. It is not possible to provide an accurate estimate of the duration of joint testing because the total duration of the testing phases depends, e.g. on
- the initial readiness of the information system
- the resources of the parties taking part in the testing
- the number of errors detected and the need to carry out retests
- the information contents to be tested.
It is possible to provide a case-specific estimate of the time schedule at the start of joint testing.
Preconditions for starting joint testing by information system suppliers
The information system supplier will assess when it is ready for starting the joint testing. The Kanta Services require that the information system supplier has carefully tested the information system to be connected to Kanta already before the start of joint testing. The production-like operation is verified in joint testing, and therefore the system must correspond to production-like implementation already at the start of joint testing. Any separate systems that may be connected to the main system must have been integrated when the system is submitted for joint testing.
To start joint testing, the information system must
- include the functionalities that meet the requirements for information systems to be connected to Kanta
- comply with the interfaces and standards of the national requirements
- be able to join the Kanta Services independently or with an integration solution independent of the supplier. The integration solution may have been arranged within the organisation or regionally.
Further requirements are that the information system supplier has
- tested all of the specified functionalities independently in the client test environments of the Kanta client test service while making sure that the information system meets the requirements in accordance with the specifications
- validated documents in the validation service
- provided Kela with the necessary information for the use of the Partners workspace (Register for joint testing)
- reported the preliminary test cases on the registration form to Kela and Kela has accepted their results
- delivered the THL system form to Kela
- when testing the system entities, delivered the architecture description of the entity to Kela
- assessed the extent of the necessary testing with the Kanta Services.
Information on integrating an application with Kanta PHR can be found on PHR site.