Contents of joint testing

Contents of joint testing

Different stages of joint testing of the Kanta services and the number of test cases vary depending on the contents to be joint tested. The contents and extent of joint testing are presented on this page.

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 Archive of Imaging Data

It is possible to carry out joint testing on radiology and ECG contents in the Archive of Imaging Data.

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.

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.


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.

Archive for social welfare services

It is possible to jointly test the deployment in the Client Data Archive for Social Welfare Services according to the latest specification version (in Finnish only). Some of the functionalities can be deployed in stages, and partial deployments can also be joint tested separately. All functionalities require the use of the most recently published schema versions of client and case documents that are in the Completed state and published in Sosmeta (  


  • Archiving, version management, invalidation and retrieval of documents according to profile
  • Structured client report entries and client documents (JSON + XHTML) can be implemented in stages. All new client documents are tested separately. Documents can be tested independently in the client test environment when they are in the Being Tested state in Sosmeta. Joint testing can begin once the documents are in the Completed state.
  • Access right to the data file as a service organiser and/or service provider
  • A shared case
  • Joint model for joining
  • Disclosure management (documents regarding the expression of will service, searching another service provider’s register) 
  • Extensive access to the data file (shelters)

Minimum requirements to start joint testing:

  • Most recent client and case document schemas (one customer/controller)
  • Valid metadata model for phase 2 (including the electronic signature of a professional, processing of a temporary personal identity code, non-disclosure for personal safety reasons and My Kanta)

The remaining requirements regarding the obligation to join must be met by 1 September 2024.

Organizations that join by the end of 2022 will be able to save phase 1 client documents until the end of 31 December 2023. After this, the Client Data Archive for Social Welfare Services will no longer accept data content that complies with phase 1. After this, old client documents and phase 2 or later client documents can be archived in the Client Data Archive (Client document metadata / Document groups, Kanta Services handbook for social services actors).

Last updated 25.10.2022