Unattributed Code Systems

Copyright Fragment

This fragment is available on index.html

This publication includes IP covered under the following statements.

Copyright and Registered Trademark Uses

External References

Type Reference Content
web tel:+358401234657 +358401234657
web hl7.fi
web www.hl7.fi IG © 2022+ HL7 Finland . Package hl7.fhir.fi.base#2.0.0-ci based on FHIR 4.0.1 . Generated 2025-03-27
Links: Table of Contents | QA Report| Version History | CC0-1.0 | Source | Propose a change
web raw.githubusercontent.com Links: Table of Contents | QA Report | Version History | CC0-1.0 | Source | Propose a change
web github.com Links: Table of Contents | QA Report | Version History | CC0-1.0 | Source | Propose a change
web github.com Links: Table of Contents | QA Report | Version History | CC0-1.0 | Source | Propose a change
web fhirblog.com Querying by location is also an option. Here the focus is on the physical location and not the organizational responsibility towards the patient. This blog post will describe the process.
web snomed.info http://snomed.info/sct|http://snomed.info/sct/11000229106
web dvv.fi The TURVAKIELTO label is the first code to be added into the Finnish CodeSystem for security labels . Many other codes are likely to be added, including codes for other data protection preferences in the Suomi.fi infrastructure and codes for permissions for health data sharing from the Kanta system . Implementer feedback regarding this approach and regarding codes that should be added is appreciated!
web www.kanta.fi The TURVAKIELTO label is the first code to be added into the Finnish CodeSystem for security labels . Many other codes are likely to be added, including codes for other data protection preferences in the Suomi.fi infrastructure and codes for permissions for health data sharing from the Kanta system . Implementer feedback regarding this approach and regarding codes that should be added is appreciated!
web www.omaolo.fi The concepts and resources are used, most notably by Omaolo symptom assessment services and AVPH ( ajanvaraus ja palveluohjain -sovellus ) scheduling service, and the scheduling API of the OMNI360 electronic health record system.
web www.solita.fi The concepts and resources are used, most notably by Omaolo symptom assessment services and AVPH ( ajanvaraus ja palveluohjain -sovellus ) scheduling service, and the scheduling API of the OMNI360 electronic health record system.
web www.cgi.com The concepts and resources are used, most notably by Omaolo symptom assessment services and AVPH ( ajanvaraus ja palveluohjain -sovellus ) scheduling service, and the scheduling API of the OMNI360 electronic health record system.
web www.kanta.fi Kanta is the Finnish national central registry of health and social welfare information. It has a specification for Palvelutapahtuma, this is typically translated as service-event or encompassing encounter.
web www.kanta.fi The scope of palvelutapahtuma is described in Kanta documentation (in Finnish). It's scope is not always the same as the encounter's. Encounter and palvelutapahtuma will overlap as concepts (depending on implementation). Some encounters clearly align with palvelutapahtuma while others don't. Palvelutapahtuma may contain multiple encounters. For example a series of treatments is considered to be a singular palvelutapahtuma , but systems most likely want to express each visit as a separate encounter (see kanta doc for the description of hoitosarja , there are other examples too).
web www.kanta.fi Kanta CDA R2 Header version 4.66 or later.
  • Descriptions of palvelutapahtuma
web www.kanta.fi Kanta HL7 V3 Medical Records specification .
  • Shows the role of palvelutapahtuma when making requests to Kanta
web thl.fi In some cases the practitioner who performed the addministration is not be the same person who recorded the action. For these cases the vaccinationRecorder extension is created. Recorder is not required information when recording vaccination to the Kanta's Patient Data Repository or Hilmo system but it may be an essential information for EHR.
web koodistopalvelu.kanta.fi All vaccinations in Finland are recorded into Kanta's Patient Data Repository and Hilmo system. Eventually these system determine the required information, at least when recording vaccination. It is highly recommended to familiarize onself with the specification when applying this profile although all of the fields may not be relevant in given use case.
web koodistopalvelu.kanta.fi The information custodian agent SHALL have a role with coding of system urn:oid:1.2.246.537.5.40172 ( eArkisto - Rekisteripitäjän laji ), i.e., whether the provider is a public or private actor. The value for the identifier SHALL be 1 for public, 2 for private.
web koodistopalvelu.kanta.fi The status of the healthcare provider ( eArkisto - Rekisteripitäjän laji ), i.e., whether the provider is a public or private actor. The value for the identifier SHALL be 1 for public, 2 for private.
web koodistopalvelu.kanta.fi The ID of the social or healthcare provider in system oid:1.2.246.537.6.203 (Valvira - Terveydenhuollon itsenäiset ammatinharjoittajat) .
web koodistopalvelu.kanta.fi The ID of the social or healthcare provider in system oid:1.2.246.537.6.202 (THL - SOTE-organisaatiorekisteri) .
web koodistopalvelu.kanta.fi The ID of the social or healthcare provider in system oid:1.2.246.537.6.40174 (eArkisto - Rekisterinpitäjärekisteri) .
web www.kanta.fi For details, please refer to the Kanta CDA R2 Header specification, version 4.66 or later, chapters 2.2.17, 2.4.21, and 2.4.22.
web hl7.fi ​ The working group was not able to reach consensus on how to present the details of the register (the type of register, rekisterin tyyppi and the register specifier, rekisterin tarkenne ). One option is to use extensions to the information custodian .agent or even to the Provenance resource instance (see the ballot version as one example). Another proposed approach is to encode this information in .entity instances (see version 1.0.0-rc21 for details). See also the discussion thread on chat.fhir.org and the GitHub issues #88 , #135 , #141 , and #163 . Implementer feedback is appreciated on how to continue work on the topic.
web hl7.fi ​ The working group was not able to reach consensus on how to present the details of the register (the type of register, rekisterin tyyppi and the register specifier, rekisterin tarkenne ). One option is to use extensions to the information custodian .agent or even to the Provenance resource instance (see the ballot version as one example). Another proposed approach is to encode this information in .entity instances (see version 1.0.0-rc21 for details). See also the discussion thread on chat.fhir.org and the GitHub issues #88 , #135 , #141 , and #163 . Implementer feedback is appreciated on how to continue work on the topic.
web github.com ​ The working group was not able to reach consensus on how to present the details of the register (the type of register, rekisterin tyyppi and the register specifier, rekisterin tarkenne ). One option is to use extensions to the information custodian .agent or even to the Provenance resource instance (see the ballot version as one example). Another proposed approach is to encode this information in .entity instances (see version 1.0.0-rc21 for details). See also the discussion thread on chat.fhir.org and the GitHub issues #88 , #135 , #141 , and #163 . Implementer feedback is appreciated on how to continue work on the topic.
web github.com ​ The working group was not able to reach consensus on how to present the details of the register (the type of register, rekisterin tyyppi and the register specifier, rekisterin tarkenne ). One option is to use extensions to the information custodian .agent or even to the Provenance resource instance (see the ballot version as one example). Another proposed approach is to encode this information in .entity instances (see version 1.0.0-rc21 for details). See also the discussion thread on chat.fhir.org and the GitHub issues #88 , #135 , #141 , and #163 . Implementer feedback is appreciated on how to continue work on the topic.
web github.com ​ The working group was not able to reach consensus on how to present the details of the register (the type of register, rekisterin tyyppi and the register specifier, rekisterin tarkenne ). One option is to use extensions to the information custodian .agent or even to the Provenance resource instance (see the ballot version as one example). Another proposed approach is to encode this information in .entity instances (see version 1.0.0-rc21 for details). See also the discussion thread on chat.fhir.org and the GitHub issues #88 , #135 , #141 , and #163 . Implementer feedback is appreciated on how to continue work on the topic.
web github.com ​ The working group was not able to reach consensus on how to present the details of the register (the type of register, rekisterin tyyppi and the register specifier, rekisterin tarkenne ). One option is to use extensions to the information custodian .agent or even to the Provenance resource instance (see the ballot version as one example). Another proposed approach is to encode this information in .entity instances (see version 1.0.0-rc21 for details). See also the discussion thread on chat.fhir.org and the GitHub issues #88 , #135 , #141 , and #163 . Implementer feedback is appreciated on how to continue work on the topic.
web www.kanta.fi For all medication related resources (Medication, MedicationAdministration, MedicationRequest, MedicationStatement), please also see the Prescription project and the related implementation guide of the Kanta system. That project contains useful definitions, examples, and sequence descriptions (mostly in Finnish).
web www.omg.org Mappings for ServD ( http://www.omg.org/spec/ServD/1.0/ )
web koodistopalvelu.kanta.fi National code server of social welfare and health care contains a registry for organizations.
web koodistopalvelu.kanta.fi National code server of social welfare and health care contains a registry for organizations.
web yhteistyotilat.fi In the context of Finnish national social and healthcare, the defined identifying information for a person are
web dvv.fi The official Personal Identifier Code ( PIC , also known as HETU ) is granted by the Digital And Population Data Services Agency. The oid for the official PIC is 1.2.246.21 .
web www.kanta.fi When an official PIC is not known or cannot be used for other reasons, a system may generate a temporary identifier . There are several ways to create an oid for the temporary identifier. The most typical ones are described in ISO OID-yksilöintitunnuksen käytön kansalliset periaatteet sosiaali- ja terveysalalla document (in Finnish).
web www.hl7.fi When an official PIC is not known or cannot be used for other reasons, a system may generate a temporary identifier . There are several ways to create an oid for the temporary identifier. The most typical ones are described in ISO OID-yksilöintitunnuksen käytön kansalliset periaatteet sosiaali- ja terveysalalla document (in Finnish).
web yhteistyotilat.fi The first method is recommended .
web dvv.fi Municipality of residence is represented with MunicipalityCode extension. Municipality means in this context the municipality which is registered as the primary residence location. The municipality of residence is always registered by the Digital and Population Data Services Agency . In most cases the address information contains the same information presented in MunicipalityCode extension but there are situations where address.city is not the same as the value in the extension. Address is better understood as contact address. More information about the subject can be found on Home municipality .
web dvv.fi The Digital and Population Data Services Agency DVV may grant a non-disclosure for personal safety . This is communicated by the TURVAKIELTO security label (see an example ).
web koodistopalvelu.kanta.fi https://koodistopalvelu.kanta.fi/codeserver/pages/classification-view-page.xhtml?classificationKey=57&versionKey=119
web koodistopalvelu.kanta.fi https://koodistopalvelu.kanta.fi/codeserver/pages/classification-view-page.xhtml?classificationKey=58&versionKey=79
web koodistopalvelu.kanta.fi https://koodistopalvelu.kanta.fi/codeserver/pages/classification-view-page.xhtml?classificationKey=763&versionKey=903
web koodistopalvelu.kanta.fi https://koodistopalvelu.kanta.fi/codeserver/pages/classification-view-page.xhtml?classificationKey=44&versionKey=118
web norden.diva-portal.org THL toimenpideluokitus is based on Nordic Classification of Surgical Procedures (NCSP) which can be found in here .
web koodistopalvelu.kanta.fi THL has a data model for Finnish diagnosis (including käyntisyy ) in code server: THL/Tietosisältö - Diagnoosit ("THL specification").
web www.kanta.fi For high level documentation, see Tiedonhallintapalvelun periaatteet ja toiminnallinen määrittely 2021, versio 1.2 .
web koodistopalvelu.kanta.fi When using Finnish ICD-10 it's usage has special rules. These are described below. For reference and detailed specifications, see Potilastiedon arkiston Kertomus ja lomakkeet version 5.11 or later.
web www.kanta.fi When using Finnish ICD-10 it's usage has special rules. These are described below. For reference and detailed specifications, see Potilastiedon arkiston Kertomus ja lomakkeet version 5.11 or later.
web dvv.fi The purpose of Municipality code is to represent the municipality of residence which is always registered by the Digital and Population Data Services Agency. The municipality of residence indicates that the person has right to use certain services provided by municipality or wellbeing services county. Municipalities are part of wellbeing services counties. Municipality of residence will also indicate in which municipality the person pays taxes.
web hl7.fi The previous version of this implementation guide depended on the International Patient Access specification, and many profile definitions of that version derive from IPA profiles. These IPA-derived profiles are now moved to the Finnish Implementation Guide for SMART App Launch .
web hl7.fi There is a separate Finnish Implementation Guide for SMART App Launch that describes how the SMART specification is applied in Finland.
web hl7.fi See also all FHIR implementation guides published by HL7 Finland and also HL7 Finland in Simplifier .
web www.kanta.fi Kanta is the Finnish national central registry of health and social welfare information, with many services available for systems, providers, and citizens. Most of both the data and the APIs in Kanta system are based on HL7 V3 standards. However, there is ongoing work to open also FHIR based access to the information.
web www.kanta.fi The part where HL7 FHIR is used the most is the Kanta PHR , a personal health record platform for storing and exchanging health and wellbeing data produced and governed by citizens. This part of Kanta is also the one most open to application developers.
web www.omaolo.fi Omaolo is a collection of services developed by DigiFinland, a publicly funded company. Omaolo has a fully HL7 FHIR based personal health record platform as its core.
web healthvillage.fi Health Village is yet another publicly funded group of services. It has built in HL7 SMART App Launch capability for interacting with third party apps.
web www.apotti.fi Apotti is a sizeable Epic installation in Finland. Epic is one of the biggest electronic health record system vendors globally.
web www.epic.com Apotti is a sizeable Epic installation in Finland. Epic is one of the biggest electronic health record system vendors globally.
web www.cgi.com The OMNI360 by CGI Finland is one of the prominent Finnish electronic health record systems and has several native FHIR APIs.
web eskosystems.fi The Esko APTJ by Esko Systems is also one of the prominent Finnish electronic health record systems. It uses several FHIR APIs internally, and offers a SMART App Launch method to interact with third party systems.
web fhir.fi The FHIR Demo 2022 showcase presented integrations implemented between a dozen platforms and more than a dozen FHIR apps, all based on HL7 FHIR. The FHIR Demo 2023 concentrated on these base profiles. FHIR Demo 2024 extended the geographical scope of the showcase to cover the Nordic countries. The latest FHIR Demo can always be found on fhir.fi/demo .
web fhir.fi The FHIR Demo 2022 showcase presented integrations implemented between a dozen platforms and more than a dozen FHIR apps, all based on HL7 FHIR. The FHIR Demo 2023 concentrated on these base profiles. FHIR Demo 2024 extended the geographical scope of the showcase to cover the Nordic countries. The latest FHIR Demo can always be found on fhir.fi/demo .
web fhir.fi The FHIR Demo 2022 showcase presented integrations implemented between a dozen platforms and more than a dozen FHIR apps, all based on HL7 FHIR. The FHIR Demo 2023 concentrated on these base profiles. FHIR Demo 2024 extended the geographical scope of the showcase to cover the Nordic countries. The latest FHIR Demo can always be found on fhir.fi/demo .
web fhir.fi The FHIR Demo 2022 showcase presented integrations implemented between a dozen platforms and more than a dozen FHIR apps, all based on HL7 FHIR. The FHIR Demo 2023 concentrated on these base profiles. FHIR Demo 2024 extended the geographical scope of the showcase to cover the Nordic countries. The latest FHIR Demo can always be found on fhir.fi/demo .
web www.hl7.fi To learn about the current status, please contact HL7 Finland . We're happy to give you an overview.
web hl7.dk the Danish DK Core
web hl7.se the Swedish Base Profiles
web invitepeople.com See the presentation slides of the session Nordic harmonization of health data , given in the Vitalis conference in May, 2023. They include an initial comparison of the Danish, Finnish, Norwegian, and Swedish base profile specifications.
web vitalis.nu See the presentation slides of the session Nordic harmonization of health data , given in the Vitalis conference in May, 2023. They include an initial comparison of the Danish, Finnish, Norwegian, and Swedish base profile specifications.
web fhir.ch the Swiss CH Core
web www.hl7.fi The profiling work is performed in a project driven by HL7 Finland . See the announcement (in Finnish), the running memo , and some more details . We warmly welcome new participants to the project. You may even be compensated for your efforts.
web www.hl7.fi The profiling work is performed in a project driven by HL7 Finland . See the announcement (in Finnish), the running memo , and some more details . We warmly welcome new participants to the project. You may even be compensated for your efforts.
web docs.google.com The profiling work is performed in a project driven by HL7 Finland . See the announcement (in Finnish), the running memo , and some more details . We warmly welcome new participants to the project. You may even be compensated for your efforts.
web fhir.fi The profiling work is performed in a project driven by HL7 Finland . See the announcement (in Finnish), the running memo , and some more details . We warmly welcome new participants to the project. You may even be compensated for your efforts.
web github.com The source code of this implementation guide is maintained in a publicly accessible repository in GitHub. Issues opened in that GitHub repo are very welcome. They help the team pick up any proposed changes or additions and to discuss them publicly.
web creativecommons.org This document is licensed under Creative Commons CC0 1.0 Universal Public Domain Dedication.
web www.iso.org ISO maintains the copyright on the country codes, and controls its use carefully. For further details see the ISO 3166 web page: https://www.iso.org/iso-3166-country-codes.html
Show Usage
web ucum.org The UCUM codes, UCUM table (regardless of format), and UCUM Specification are copyright 1999-2009, Regenstrief Institute, Inc. and the Unified Codes for Units of Measures (UCUM) Organization. All rights reserved. https://ucum.org/trac/wiki/TermsOfUse
Show Usage
web koodistopalvelu.kanta.fi The Finnish Institute for Health and Welfare maintains a National code server of social welfare and health care , only in Finnish language. The standardised data structures required by the electronic client data systems in social welfare and health care as well as the central code sets of the statistical and register data collection are all published on the code server.
web thl.fi Read more (in Finnish).
web koodistopalvelu.kanta.fi FinLOINC - The Physiological Measurements classification contains results and findings of clinical measurements that describe the patient's condition. FinLOINC is based on the Logical Observation Identifiers Names and Codes (LOINC®) nomenclature maintained by Regenstrief Institute, covering only a small part of it.
web koodistopalvelu.kanta.fi Most systems and services in Finland use the laboratory test codes and names specified in the laboratory test name set by Kuntaliitto.
web www.whocc.no Finland uses the ATC classification for codifying medicines. See the Finnish localized version . The classification divides drugs into groups according to which organ or organ system they affect and by their chemical, pharmacological and therapeutic properties
web www.fimea.fi Finland uses the ATC classification for codifying medicines. See the Finnish localized version . The classification divides drugs into groups according to which organ or organ system they affect and by their chemical, pharmacological and therapeutic properties
web wiki.vnr.fi Finland uses the Nordic Article Number ( VNR ) system for identification codes of specific articles of medicine with marketing authorisation in the Nordic countries.
web github.com You can track the changes between released snapshot versions through the Previous Version Comparison section of the QA report . You can also check changes between ballot and release versions through the releases in GitHub.
web hl7.fi Dependencies to International Patient Access (IPA) specification have been moved from the base profiles to the Finnish Implementation Guide for SMART App Launch .
web fhir.fi The latest version of the master branch of the source code repository for this implementation guide is published at https://fhir.fi/finnish-base-profiles/ .
web fhir.github.io You can also browse the list of all IG builds .

Internal Images