Joint testing is carried out on contents in accordance with the publication schedule (in Finnish only), in which case the timetable of joint testing complies with the timetable presented in the publication schedule. The joint testing need may also arise from system changes carried out by the information system supplier or Kela. In that case, the timetable of joint testing is agreed separately.
The Imaging Data Repository
It is possible to carry out joint testing on radiology and ECG contents in the Imaging Data Repository.
In the following phases, it is possible to carry out joint testing on the extensions of information contents, which include
- visible light images (fundus images as a pilot)
- oral healthcare imaging.
Kanta PHR
With respect to Kanta PHR, it is possible to carry out joint testing on implementations in accordance with different FHIR standard versions. New operators are required to have an implementation in accordance with the latest version of the FHIR standard.
Wellbeing applications’ patient data interface
In the Wellbeing applications’ patient data interface service, it is possible to carry out joint testing of the following data content retrieved from the Patient Data Repository:
- Diagnoses
- Risks
- Procedures
- Physiological measurements
- Vaccination data
- Laboratory information
- Health and care plans
- Patient record texts
Patient Data Repository
In the Patient Data Repository it is possible to carry out joint testing on the following contents:
- archiving and retrieval:
- diagnoses
- risks
- procedures
- vaccination
- physiological measurements
- imaging
- laboratory
- declaration of disclosure
- raising the level of the specification version 2014–2016
- declarations of intent and management of data sharing
- oral healthcare
- Kela’s medical certificates
- certificates in accordance with the Mental Health Act
- medical certificate on fitness to drive
- outsourced service authorisation
- referral and epicrisis
- health and care plan
- optometry
- utilisation of key structured health data from the Patient Data Management Service
- acting on behalf of a minor.
In the document ‘Joint testing of the contents of the Patient Data Repository’, are described the contents of the Patient Data Repository that are to be jointly tested, the scope of the testing and the testing stages. The document also describes the dependencies between the different kinds of contents and provides tips on how to facilitate the creation of contents for the Patient Data Repository as well as the planning of joint testing of them.
The test cases cover a range of basic test sets for each content. Before the joint testing is started, Kela will in cooperation with the system supplier identify the user profile(s) needed for the joint testing of the patient data system and other data necessary for the testing. This ensures that the test content is comprehensive and focuses on the right aspects.
Prescription
With respect to the Prescription service, it is possible to carry out joint testing on the implementation in accordance with the latest definition version (in Finnish only).
Testing can be carried out with two different profiles:
- the pharmacy system
- the patient data system.
Client Data Repository for Social Welfare Services
It is possible to jointly test the deployment of the Client Data Repository for Social Welfare Services in accordance with the obligation to join Kanta Services. The testing uses the latest specification versions (in Finnish only) and the final schema versions of the documents published in Sosmeta according to the intended use and profile of the system.
Mandatory content:
- Basic functionalities of the Client Data Repository for Social Welfare Services and the latest valid metadata
- Client report entries
- Access right to the data file as a service organiser
- Access right to the data file as a service provider
- Structural client documents by service function
- Archiving and/or search functions in previous client documents
- Disclosure management: Documents regarding the expression of will service
- Disclosure management: Searching another service provider’s data file
- Disclosure management: disclosure notices
Optional content:
- A shared case
- Extensive access right to the data file, access right to the data file must be implemented
- Joint model for joining, parallel model for joining, access right to the data file must be implemented
- Self-testing is sufficient, but the message must be submitted for review by joint testing
- Client’s electronic signature
Joint-testing entities can be tested in parts. A joint-testing statement and report are generated about the tested content.
Organisations that have joined by the end of 2022 will be able to save phase 1 client documents until the end of the obligation period for joining. After this, the Client Data Repository for Social Welfare Services will no longer accept data content that complies with phase 1.