Finnish Base Profiles
1.0.1-cibuild - ci-build Finland flag

Finnish Base Profiles - Local Development build (v1.0.1-cibuild) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

Artifacts Summary

This page provides a list of the FHIR artifacts defined as part of this implementation guide.

Structures: Abstract Profiles

These are profiles on resources or data types that describe patterns used by other profiles, but cannot be instantiated directly. I.e. instances can conform to profiles based on these abstract profiles, but do not declare conformance to the abstract profiles themselves.

FI Base InformationCustodian

This is a Finnish abstract base profile for the Provenance resource, used to communicate the custodian of information (rekisterinpitäjä).

Structures: Resource Profiles

These define constraints on FHIR resources for systems conforming to this implementation guide.

An imaginary profile for Kanta system, specifying things apart from the information custodian

This is one way in which a system might use the Finnish Base Information Custodian profile. This profile defines other constraints. The profile KantaDocumentMetadata combines the requirements.

An imaginary profile for Kanta system, utilizing the Finnish Base Information Custodian profile

This is one way in which a system might use the Finnish Base Information Custodian profile. Kanta has expressed the wish to have only one big Provenance resource containing all document metadata. This can be accomplished by creating a profile based on the Finnish Base Provenance profile and imposing the Finnish Base Information Custodian profile.

FI Base Appointment

This is the Finnish base profile for the Appointment resource.

FI Base Condition

This is the Finnish base profile for the Condition resource.

FI Base Encounter

This is the Finnish base profile for the Encounter resource.

FI Base EpisodeOfCare

This is the Finnish base profile for the EpisodeOfCare resource.

FI Base HealthcareService

This is the Finnish base profile for the HealthcareService resource.

FI Base Information Custodian (Individual Provider)

This is the Finnish base profile for the Provenance resource, used to communicate an individual practitioner as the custodian of information (rekisterinpitäjä).

FI Base Information Custodian (Private Organization)

This is the Finnish base profile for the Provenance resource, used to communicate a private organization as the custodian of information (rekisterinpitäjä).

FI Base Information Custodian (Public Organization)

This is the Finnish base profile for the Provenance resource, used to communicate a public organization as the custodian of information (rekisterinpitäjä).

FI Base Location

This is the Finnish base profile for the Location resource.

FI Base Medication

This is the Finnish base profile for the Medication resource for other than patient access use cases.

FI Base MedicationAdministration

This is the Finnish base profile for the MedicationAdministration resource.

FI Base MedicationRequest

This is the Finnish base profile for the MedicationRequest resource, for other than patient access use cases.

FI Base MedicationStatement

This is the Finnish base profile for the MedicationStatement resource.

FI Base Observation

This is the Finnish base profile for the Observation resource.

FI Base Organization

This is the Finnish base profile for the Organization resource.

FI Base Patient

This is the Finnish base profile for the Patient resource.

FI Base Patient Medication

This is the Finnish base profile for the Medication resource for patient access use case.

FI Base Patient MedicationRequest

This is the Finnish base profile for the MedicationRequest resource for the patient access use case.

FI Base Practitioner

This is the Finnish base profile for the Practitioner resource.

FI Base PractitionerRole

This is the Finnish base profile for the PractitionerRole resource.

FI Base Provenance

This is the Finnish base profile for the Provenance resource.

FI Base Reason for Care (encounter-diagnosis and reason for visit)

This is the Finnish base profile for the encounter-diagnosis and (nurse asserted) reason for visit Conditions.

FI Base Schedule

This is the Finnish base profile for the Schedule resource.

FI Base Slot

This is the Finnish base profile for the Slot resource.

Fi Base Immunization

This is a base profile for Finnish Immunization resource.

Fi Base Procedure

The Base profile for Finnish Procedure resource.

Structures: Extension Definitions

These define constraints on FHIR data types for systems conforming to this implementation guide.

Categorization of the type of accident

Encoded categorization of the type of accident leading to injury, illness or death.

Cause of an adverse effect

Encoded information on the cause of an adverse effect, when involving a procedure or medication

Endocrinological disorder

Code for Endocrinological disorder.

External cause for diagnosis

External cause for diagnosis.

Medication that caused this condition

Encoded information of medication that caused this condition. Uses ATC-coding.

Municipality Code

Extension for home municipality. Home municipality is relevant for ex. in billing and listing available healthcare services, and for statistical purposes. It it not necessarily the place where a patient lives, rather closer to where they pay their taxes.

Patient Profession Extension

Extension for presenting patient profession.

Permanence of condition

Encoded information of whether this is the permanent.

Primary condition for encounter

Encoded information of whether this is the primary/main condition for encounter.

Type of physical exercise during which injury occurred.

Encoded information of the type of physical exercise during which injury occurred.

Vaccination Recorder

Vaccination recorder may not be the same person who performed the addministration.

Terminology: Value Sets

These define sets of codes used by systems conforming to this implementation guide.

Example value set for provenance roles

This example value set contains the systems that can be used for agent roles in Kanta profiles

Finnish ValueSet for security labels in accordance with finnish authorities

This is the ValueSet for security labels in accordance with finnish authorities.

Finnish ValueSet for systems of registry specifiers

This value set contains the systems that can be used to identify the registry specifier for information custodianship.

Terminology: Code Systems

These define new code systems used by systems conforming to this implementation guide.

Finnish CodeSystem for security labels

This is the CodeSystem for security labels in accordance with finnish authorities.

Example: Example Instances

These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.

1 tabletti 2 kertaa päivässä

An example MedicationRequest from Kanta Prescription API

1 tabletti 2 kertaa päivässä 5 päivän ajan 15.1.2021 alkaen

An example MedicationRequest from Kanta Prescription API

1 tabletti 2 kertaa päivässä 5-7 päivän ajan 15.1.2021 alkaen

An example MedicationRequest from Kanta Prescription API

1-2 tablettia 1-3 kertaa päivässä

An example MedicationRequest from Kanta Prescription API

1-2 tablettia kerran päivässä

An example MedicationRequest from Kanta Prescription API

2 tablettia aamulla ja 1 tabletti illalla 6 päivän ajan

An example MedicationRequest from Kanta Prescription API

A high level organization

Organization on Wellbeing Services County level

A named bed

Example of a bed recorded with the Location resource.

A simple practitioner role

An example PractitionerRole instance from Kanta Prescription API

A simple provenance example

An example Provenance resource instance from Kanta

A test example demonstrating that validation works

This example does not have the role for the agent from system urn:oid:1.2.246.537.5.40172, as would be mandated by the Finnish Base Information Custodian profile. QA report is expected to show an error.

An imaginary example of a Provenance resource instance conforming to the imaginary metadata profile for Kanta system

This example demonstrates one way in which a system might use the Finnish Base Information Custodian profile.

An imaginary example of a Provenance resource instance conforming to the imaginary metadata profile for Kanta system, using the kanta code also for the custodian agent

This example demonstrates one way in which a system might use the Finnish Base Information Custodian profile.

Another Encounter that is part of palvelutapahtuma

An example of a FI Base encounter which is part of another encounter that corresponds to palvelutapahtuma in Kanta.

Another test example demonstrating that validation works

This example does not have a role with the code system specified by Kanta. QA report is expected to show an error.

Biopsy of Colon procedure example

Sub-procedure for Colotomy procedure.

Codified healthcare service

HealthcareService example which describes general practitioner services by using THL code systems.

Condition - an example diagnosis

An example of a diagnosis using the FiBaseReasonForCare profile. This diagnosis is asserted by a clinician.

Condition - an example diagnosis with an adverse effect.

An example of a diagnosis using the FiBaseReasonForCare profile. This diagnosis demonstrates a case that has an adverse effect.

Condition - an example diagnosis with external cause, accident and medication information.

An example of a diagnosis using the FiBaseReasonForCare profile. This diagnosis demonstrates a case that has external cause, accident and medication information.

Custodian of information (rekisterinpitäjä), an individual provider

Example of Provenance that communicates a private individual healthcare provider as the custodian of information for an episode of care.

Custodian of information (rekisterinpitäjä), private occupational healthcare

Example of Provenance that communicates a private occupational healthcare organization as the custodian of information for an episode of care.

Custodian of information (rekisterinpitäjä), public healthcare

Example of Provenance that communicates a public healthcare organization as the custodian of information for an episode of care.

Encounter - example primary care organization

An example of a FI Base organization, a surgical ward. The partOf reference removed for brevity.

Encounter - patient is currently receiving care at a ward treating surgical patients

An example of a FI Base encounter where a patient is currently receiving care at a ward.

Encounter - patient primary care visit

An example of a FI Base encounter where a patient has completed a visit in primary care.

Encounter that is a palvelutapahtuma in Kanta registry

An example of a FI Base encounter which corresponds 1-1 to palvelutapahtuma in Kanta. Identifier with use=official marks the OID of palvelutapahtuma. Has sub-encounters.

Encounter that is part of palvelutapahtuma

An example of a FI Base encounter which is part of another encounter that corresponds palvelutapahtuma in Kanta.

Episode of care - with provenance

Example of episode of care. A provenance example links to this.

Free slot (kertakäynti yleislääkärillä)

Example of a free slot with reference to Schedule and information about service category, service type and appointment type presented in THL code system format.

GP appointment

Example of an appointment with general practitioner.

Kanta PHR - Insulin dosage mandatory

An example insulin dosage with mandatory elements.

Kanta PHR - Insulin dosage optional

An example insulin dosage with optional elements.

Kanta PHR - MET measurement mandatory

An example MET measurement with mandatory elements.

Kanta PHR - MET measurement optional

An example MET measurement with optional elements.

Kanta PHR - blood glucose mandatory

An example blood glucose measurement with mandatory elements.

Kanta PHR - blood glucose optional

An example blood glucose measurement with optional elements.

Kanta PHR - blood glucose result as text

This is an example, where measurement device has failed to measure numerical value for the blood glucose but the device still can store some result in the narrative element. In this case code 'astext' must be used in dataAbsentReason.coding.code.

Kanta PHR - blood glucose with data absent

This is an example, where measurement device has failed to measure blood glucose reading. In this case 'error' must be used in dataAbsentReason.coding.code.

Kanta PHR - blood pressure mandatory

An example blood pressure measurement with mandatory elements.

Kanta PHR - blood pressure optional

An example blood pressure measurement with optional elements.

Kanta PHR - body height optional

An example body height measurement with optional elements.

Kanta PHR - body weight mandatory

An example body weight measurement with mandatory elements.

Kanta PHR - body weight optional

An example body weight measurement with optional elements.

Kanta PHR - calorie intake mandatory

An example calorie intake measurement with mandatory elements.

Kanta PHR - calorie intake optional

An example calorie intake measurement with optional elements.

Kanta PHR - carbohydrate intake mandatory

An example estimated carbohydrate intake measurement with mandatory elements.

Kanta PHR - carbohydrate intake optional

An example estimated carbohydrate intake measurement with optional elements.

Kanta PHR - exercise tracking mandatory

An example exercise tracking measurement with mandatory elements.

Kanta PHR - exercise tracking optional

An example exercise tracking measurement with optional elements.

Kanta PHR - patient 3

An example patient for Kanta PHR.

Kanta PHR - physical activity mandatory

An example physical activity measurement with mandatory elements.

Kanta PHR - physical activity optional

An example physical activity measurement with optional elements.

Kanta PHR - step count mandatory

An example step count measurement with mandatory elements.

Kanta PHR - step count optional

An example step count measurement with optional elements.

Karen van der Hentenryck

An example patient from Kanta Prescription API

Lars van der Knaapi

An example practitioner from Kanta Prescription API

Licenced physician

Example of Licensed Physician from CGI Pegasos EHR.

Licenced physician in primary care

This is an example of PractitionerRole profile. The example describes the service which practitioner is performing in a specific location.

Lääke tauolla 1.3.2020 - 30.6.2020. Taukoa edeltävä annostus: 25 mg klo 08:00 10 päivän ajan ihon alle

An example MedicationRequest from Kanta Prescription API

Maanantaisin 1 tabletti ja tarvittaessa keskiviikkoisin 0,5 tablettia 01.06.2020 - 31.12.2020

An example MedicationRequest from Kanta Prescription API

MedicationAdministration example of insulin basal dose

A basal dose of fast-acting insulin, administred with an insulin pump. Conforms to the Kanta PHR profile, version STU3. In Swedish.

MedicationAdministration example of insulin dose

A bolus dose of fast-acting insulin, administred with an insulin pump. In Finnish.

MedicationAdministration example of temporary basal rate

A temporarily adjusted basal dose of fast-acting insulin, administred with an insulin pump. Conforms to the Kanta PHR profile. In English.

Myyntiluvallinen lääkevalmiste

An example Medication instance from Kanta Prescription API

Myyntiluvallinen lääkevalmiste, joka on PKV-lääke

An example Medication instance from Kanta Prescription API

Organization - example of a parent organization

An example of a FI Base organization. Acts as a parent organization for another.

Organization - example primary care organization

An example of a FI Base organization, a doctor's reception office. Data is from national SOTE-Rekisteri.

Outpatient clinic

Example of surgery outpatient clinic with reference to an organization.

Patient - with the MunicipalityCode extension.

An example of a FI Base patient with the MunicipalityCode extension.

Patient generated glucose observations and insulin administrations as a bundle, in English

A Bundle of resources uploaded by a patient from a insulin delivery system containing both a continuous glucose sensor and an insulin pump. Conforms to Kanta PHR R4 profiles.

Patient generated glucose observations and insulin administrations as a bundle, in Finnish

A Bundle of resources uploaded by a patient from a insulin delivery system containing both a continuous glucose sensor and an insulin pump.

Patient generated glucose observations and insulin administrations as a bundle, in Swedish

A Bundle of resources uploaded by a patient from a insulin delivery system containing both a continuous glucose sensor and an insulin pump. Conforms to Kanta PHR STU3 profiles.

Patient with a TURVAKIELTO security label.

An example of a FI Base patient that has the TURVAKIELTO security label indicating non-disclosure for personal safety reasons.

Procedure Colotomy example

This example describes main procedure, colotomy, with reference to sub-procedure.

Provenance example for Kanta

This example resource shows how information custodianship can be implemented with the support of the Finnish base profiles. It is derived from a provided example.

SNOMED CT coded Schedule

This is a Schedule example for appointment book. All of the used codes are from SNOMED code system.

Simple Organization example

An example Organization from Kanta Prescription API

Simple medication statement example

Patient states they are taking long acting insulin (Lantus), but not the amount.

Tarvittaessa 1-2 tippaa 3-4 tunnin välein

An example MedicationRequest from Kanta Prescription API

Tarvittaessa 2 tablettia 3 kertaa viikossa 16.2.2021 alkaen

An example MedicationRequest from Kanta Prescription API

Testi terveysasema

An example Organization from Kanta Prescription API

Vaccination for TBE

An example vaccination against TBE.

Other

These are resources that are used within this implementation guide that do not fit into one of the other categories.

A dummy patient entry

A patient id supporting other examples, not included in the guide.

A dummy patient entry

A patient id supporting other examples, not included in the guide.

A dummy patient entry

A patient id supporting other examples, not included in the guide.

A dummy patient entry

A patient id supporting other examples, not included in the guide.

A dummy patient entry

A patient id supporting other examples, not included in the guide.

A dummy patient entry

A patient id supporting other examples, not included in the guide.

A dummy patient entry

A patient id supporting other examples, not included in the guide.

A dummy patient entry

A patient id supporting other examples, not included in the guide.