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

In the first stage of the archive of imaging data, it is possible to carry out joint testing on the radiology contents. Joint testing of the first stage can be carried out with periods in accordance with the publication schedule.

In the second stage, it is possible to carry out joint testing on the extensions of information contents, which include

  • ECG
  • visible light images (fundus images as a pilot)
  • oral healthcare imaging.

Patient Data Repository

Information contents of the first stage in accordance with the stagewise decree:

  • archiving in primary and secondary health care
    • diagnoses
    • risks
    • procedures
    • vaccination
    • physiological measurements
  • consent management and searches
  • imaging
  • laboratory.

Information contents of the second stage:

  • archiving in oral healthcare
  • Kela’s medical certificates
  • certificates in accordance with the Mental Health Act
  • outsourced service authorisation
  • referral and epicrisis
  • health and care plan.

It is also possible to carry out joint testing on information contents not included in the stagewise decree. These contents include optometry and medical certificate on fitness to drive. 

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

New rounds of joint testing can no longer be initiated on the basis of first-stage functionalities.  New functionalities can be introduced in stages and partial implementations can also be tested separately.
Second-stage functionalities and potential dependencies:

  • entries in client histories must be in a structured format, and an enriched client document and a second-stage (or later) metadata model must be available.
  • universal requirement: a new version of the case document
  • electronic signature of the professional: no dependencies but required when creating second-stage documents that require a professional’s signature.
  • processing of documents if access to personal data is restricted: An enriched client document is required
  • processing of temporary individualisation codes, no dependencies
  • use of the second-stage (or later) document metadata model: second-stage documents and an enriched client document must be available. Required when archiving second-stage documents or case history entries.
  • an enriched version of the summary of client data. The client data system must have capability to receive and interpret it if searched
  • structured storage format for client documents (JSON + XHTML): second-stage documents and an enriched client document must be available
  • functionality for using the service provider’s register with register access rights, no dependencies
  • viewing client data on the My Kanta Pages.

With the introduction of the second-stage functionalities, also the profiles will be modified:

  • system for the processing of social welfare client data
  • application producing outgoing social welfare client data
  • application or service retrieving data from the client data archive for social welfare services
  • application or service delivering data into the client data archive for social welfare services.

The new profiles will be activated in April 2020. Old profiles will not expire but rather their functionalities or information contents will be given a specified period of validity. New functionalities or information contents will be added or updated to the profiles as they become available in the client testing environment. All certifications conforming to existing profiles will remain effective as per normal. A requirement for the certification of a new profile is that new versions of the case and client documents, procedures for the processing of restricted-access data and a second-stage (or later) document metadata model have been implemented.  Also required will be a structured case history entry and client documents in either the PDF/A or JSON + XHTML format with the option of a social welfare professional’s electronic signature.

Last updated 19.05.2020