It may in some cases be necessary for you as a social welfare and health care service provider to verify the technical functionality of your information system in a scenario where you are already using the Kanta Services.
In such a scenario, you may need to check the functions of your information system in the production environment, which may result in the actions taken being visible in the production of Kanta Services, for instance as messaging.
Verifying technical functionality may be necessary due to:
- a change of information system
- a change of version
- other system updates
- verifying technical communication between units
If verifying functionality will have an impact on the Kanta Services, do the following
Verification of technical functionality is undertaken on the basis of a needs assessment by the service provider and/or system supplier. You do not need to submit a plan to Kela for the actions to be taken, and you do not need to report the verification actions taken to Kela after the fact.
If you encounter any problems when verifying technical functionality, you must contact your system supplier. The system supplier will then, if necessary, contact technical support for the Kanta Services at Kela.
Make use of test cases
In verifying technical functionality, you may consult the guidelines for and test cases of deployment tests (Patient Data Repository and Client Data Archive) and production readiness verification (Prescription Service). Service providers must perform verification actions to the extent they consider necessary to prove technical functionality.
Use Kela's test user IDs
Only test user IDs in the 900 series provided by Kela may be used for verifying technical functionality in the production environment.
Kela has issued test user IDs for the production environment to system suppliers. You may request these IDs from your system supplier.
Always follow these instructions when using test user IDs for verifying technical functionality:
- Use official test user IDs issued by Kela, whose OID codes are in the format 18.104.22.168.DDMMYY-9000. Do not use temporary user IDs.
- Do not combine two test user IDs in the production environment.
- It is strictly prohibited to use user IDs other than test user IDs in the 900 series in the Kanta Services production environment.
Check that data are saved using the Archivist user interface
When verifying technical functionality, it may be necessary to check that data have been appropriately saved in the Patient Data Repository or Client Data Archive. The easiest way to do this is using the Archivist user interface.
System tests must be run in a test environment
Service providers should note that verifying technical functionality in production is not the same thing as system testing.
You must not perform system testing in the production environment. The systematic testing of information systems in the context of system development, for instance, must always be carried out in a test environment.
If any major forthcoming system changes will have an impact on the Kanta Services or the service interfaces, the system supplier must notify Kela of these changes. Kela will then assess whether joint testing of the changes will be needed.
Verification of technical functionality is not a replacement for deployment testing
Verification of technical functionality is a procedure carried out when the Kanta Services are already in use.
If a service or a function is only just being deployed, its functionality must be verified with:
- a deployment test (Patient Data Repository and Client Data Archive)
- verification of production readiness (Prescription Service)
Deployment tests and verification of production readiness are to be carried out at the end of the deployment process, before starting production use. There are varying requirements for deployment tests and verification of production readiness, and service providers should check the relevant web pages for guidelines.
Verification of technical functionality is not a replacement for deployment testing.