|
Type
|
Reference
|
Content
|
|
web
|
hl7.no
|
IG © 2025+ HL7 Norge
.
Package hl7.fhir.no.kommune#0.3.0 based on FHIR 4.0.1
.
Generated 2026-10-02
Links: Table of Contents |
QA Report
|
|
web
|
finnkode.helsedirektoratet.no
|
An activity may be described directly in activity.detail
or reference a separate request through activity.reference
. These are not used together in the same activity. The service is described in activity.detail.code
or ServiceRequest.code
, respectively. KPR service type (9151)
may be used when the service concept matches.
|
|
web
|
finnkode.helsedirektoratet.no
|
type
describes the contact form, such as a home visit. serviceType
describes the service within which the visit occurs. KPR service type (9151)
may be used in serviceType
when the service concept matches.
|
|
web
|
siframework.org
|
Quality Improvement and Clinical Knowledge (QUICK)
|
|
web
|
finnkode.helsedirektoratet.no
|
code
describes what is requested. KPR service type (9151)
may be used when the service concept matches. The binding is example
, while the element is mandatory.
|
|
web
|
finnkode.helsedirektoratet.no
|
Two illustrative codes from Service type in KPR municipal service allocation (code system 9151). The profiles use the value set with example binding strength; it is not a complete service catalogue. See the full code system and validity dates in FinnKode
.
|
|
web
|
open-docs.demo.aidn.no
|
Open Aidn
is a concrete example of a vendor API for municipal integrations. The documentation was reviewed on 2 October 2026. It describes the endpoints, searches and OAuth 2.0 scopes supported by Open Aidn. It also states that the service currently uses selected fields from the FHIR R4 base resources and that formal Aidn profiles may be published later.
|
|
web
|
open-docs.demo.aidn.no
|
Patient
|
|
web
|
open-docs.demo.aidn.no
|
EpisodeOfCare
and
Encounter
|
|
web
|
open-docs.demo.aidn.no
|
EpisodeOfCare
and
Encounter
|
|
web
|
open-docs.demo.aidn.no
|
Observation
|
|
web
|
open-docs.demo.aidn.no
|
Task
|
|
web
|
hl7norway.github.io
|
IG versioning (HL7 Norway)
|
|
web
|
hl7norway.github.io
|
API versioning (HL7 Norway)
|
|
web
|
hl7norway.github.io
|
Model versioning (HL7 Norway)
|
|
web
|
hl7norway.github.io
|
A good implementation guide (HL7 Norway)
|
|
web
|
hl7norway.github.io
|
Identifier search in REST operations (HL7 Norway)
|
|
web
|
www.nhn.no
|
Trust framework (Norsk helsenett, NHN)
|
|
web
|
utviklerportal.nhn.no
|
Shared EHR modernization (NHN Developer Portal)
|
|
web
|
utviklerportal.nhn.no
|
Municipal interoperability services (NHN Developer Portal)
|
|
web
|
utviklerportal.nhn.no
|
Velferdsteknologisk knutepunkt (VKP) (NHN Developer Portal)
|
|
web
|
open-docs.demo.aidn.no
|
Open Aidn – getting started
|
|
web
|
open-docs.demo.aidn.no
|
Open Aidn – authentication and access
|
|
web
|
hl7norway.github.io
|
See HL7 Norway's versioning guidance
and Semantic Versioning
.
|
|
web
|
semver.org
|
See HL7 Norway's versioning guidance
and Semantic Versioning
.
|
|
web
|
www.rfc-editor.org
|
RFC 2119 - Key words for use in RFCs
|
|
web
|
www.rfc-editor.org
|
RFC 8174 - Ambiguity of Uppercase vs Lowercase
|
|
web
|
www.iso.org
|
ISO/IEC Directives - foreword supplementary information
|
|
web
|
hl7norway.github.io
|
IG and documentation (HL7 Norway)
|
|
web
|
hl7norway.github.io
|
HL7 Norway FHIR process
|
|
web
|
fhir.kl.dk
|
Denmark KL Core: Artifacts
|
|
web
|
fhir.kl.dk
|
Denmark KL Core: KLCommonCareSocialEncounter
|
|
web
|
fhir.kl.dk
|
Denmark KL Core: KLCommonCareSocialCarePlan
|
|
web
|
oslokommune.github.io
|
Oslo municipality Patient Journal API: municipal-encounter
|
|
web
|
oslokommune.github.io
|
Oslo municipality Patient Journal API: municipal-careplan
|
|
web
|
oslokommune.github.io
|
Oslo municipality Patient Journal API: municipal-observation
|
|
web
|
utviklerportal.nhn.no
|
NHN (Norwegian Health Network): Patient's measurement data
|
|
web
|
utviklerportal.nhn.no
|
NHN (Norwegian Health Network): VKP and Patient's measurement data
|
|
web
|
health.ec.europa.eu
|
The first group of priority data for primary use is covered from 2029, with further categories from 2031; see the European Commission's timeline
.
|
|
web
|
www.regjeringen.no
|
Norwegian implementation follows the EEA and legislative processes. The Government opened consultation on implementation in Norwegian law on 8 June 2026; its EEA note of 10 June still described assessment for incorporation. EU entry into force therefore does not establish that all requirements already apply to Norwegian municipalities. See the consultation
and EEA note
. Status checked on 31 August 2026.
|
|
web
|
www.regjeringen.no
|
Norwegian implementation follows the EEA and legislative processes. The Government opened consultation on implementation in Norwegian law on 8 June 2026; its EEA note of 10 June still described assessment for incorporation. EU entry into force therefore does not establish that all requirements already apply to Norwegian municipalities. See the consultation
and EEA note
. Status checked on 31 August 2026.
|
|
web
|
health.ec.europa.eu
|
European Commission: European Health Data Space Regulation (EHDS) - status and timeline
|
|
web
|
health.ec.europa.eu
|
European Commission: My rights over my health data - definition of primary and secondary use
|
|
web
|
www.consilium.europa.eu
|
Council of the EU: EHDS adopted - press release 21 January 2025
|
|
web
|
hl7norway.github.io
|
HL7 Norway: Best practice
|
|
web
|
hl7norway.github.io
|
HL7 Norway: HL7 Norway FHIR process
|
|
web
|
hl7.eu
|
HL7 Europe Base and Core 2.0.0
provides European reference patterns for FHIR R4. It describes flexible Base profiles and more constrained Core profiles that can support reuse across European and national initiatives, including EHDS alignment.
|
|
web
|
www.kl.dk
|
Denmark has established the Joint Municipal Information Model
(Danish: Fælleskommunal Informationsmodel, FKI) through Local Government Denmark (KL)
as a shared information model for municipal health, elderly care and social services. The purpose of FKI is to support better data sharing and reuse of documentation between municipal professional systems, thereby reducing double registration and inconsistent terminology.
|
|
web
|
digital.nhs.uk
|
In the United Kingdom, UK Core
is established as a national FHIR base layer through National Health Service (NHS) England
. UK Core consists of cross-sector FHIR R4 profiles, extensions and terminology, and is used across England, Scotland, Wales and Northern Ireland to support consistent information flows between sectors.
|
|
web
|
www.kl.dk
|
KL: Joint Municipal Information Model (FKI)
|
|
web
|
fhir.kl.dk
|
KL: KLCore (FKI-FHIR IG)
|
|
web
|
fhir.kl.dk
|
KL: KLGateway (reporting and minimum data)
|
|
web
|
hl7.eu
|
HL7 Europe: Base and Core FHIR IG 2.0.0
|
|
web
|
digital.nhs.uk
|
NHS England: FHIR UK Core
|
|
web
|
insightcollective.socialcare.wales
|
Social Care Wales: FHIR in social care
|
|
web
|
finnkode.helsedirektoratet.no
|
The domains below come from Functional domain (9111)
. Results use Functional value (9165)
, with separate scales for vision (9166)
and hearing (9167)
. Numbers in parentheses identify code systems. The specific codes and full code system identifiers are available in the JSON view of each example.
|
|
web
|
finnkode.helsedirektoratet.no
|
The domains below come from Functional domain (9111)
. Results use Functional value (9165)
, with separate scales for vision (9166)
and hearing (9167)
. Numbers in parentheses identify code systems. The specific codes and full code system identifiers are available in the JSON view of each example.
|
|
web
|
finnkode.helsedirektoratet.no
|
The domains below come from Functional domain (9111)
. Results use Functional value (9165)
, with separate scales for vision (9166)
and hearing (9167)
. Numbers in parentheses identify code systems. The specific codes and full code system identifiers are available in the JSON view of each example.
|
|
web
|
finnkode.helsedirektoratet.no
|
The domains below come from Functional domain (9111)
. Results use Functional value (9165)
, with separate scales for vision (9166)
and hearing (9167)
. Numbers in parentheses identify code systems. The specific codes and full code system identifiers are available in the JSON view of each example.
|
|
web
|
www.fhi.no
|
This covers six of the 20 functional domains. Scores illustrate FHIR data; clinical scoring follows FHI's guidance
and the code system descriptions.
|
|
web
|
www.nhn.no
|
Use of PLO messages with health trusts (Norwegian Health Network)
|
|
web
|
open-docs.demo.aidn.no
|
Open Aidn
|
|
web
|
www.fhi.no
|
KPR municipal service allocation
(KPR KTT):
Provides national code systems for service type, functional assessment, decisions and reporting. KPR KTT was previously referred to as KPR IPLOS and KPR health and care; the former IPLOS register was a separate register. See FHI's description of KPR KTT
.
|
|
web
|
finnkode.helsedirektoratet.no
|
Service type in KPR municipal service allocation (9151)
is relevant when the information actually describes a service in that code system:
|
|
web
|
finnkode.helsedirektoratet.no
|
Functional domain (9111)
, such as personal hygiene or vision.
|
|
web
|
finnkode.helsedirektoratet.no
|
Functional value (9165)
. Vision and hearing have separate scales: vision value (9166)
and hearing value (9167)
.
|
|
web
|
finnkode.helsedirektoratet.no
|
Functional value (9165)
. Vision and hearing have separate scales: vision value (9166)
and hearing value (9167)
.
|
|
web
|
finnkode.helsedirektoratet.no
|
Functional value (9165)
. Vision and hearing have separate scales: vision value (9166)
and hearing value (9167)
.
|
|
web
|
finnkode.helsedirektoratet.no
|
FinnKode
and FHI's reporting guide
are the sources for meaning, validity and reporting rules. The FHIR examples demonstrate interoperability and are not a KPR KTT reporting format. Example codes were checked on 1 September 2026.
|
|
web
|
www.fhi.no
|
FinnKode
and FHI's reporting guide
are the sources for meaning, validity and reporting rules. The FHIR examples demonstrate interoperability and are not a KPR KTT reporting format. Example codes were checked on 1 September 2026.
|
|
web
|
www.fhi.no
|
Reporting guide for municipal service allocation (FHI)
|
|
web
|
finnkode.helsedirektoratet.no
|
FinnKode – national code systems (Norwegian Directorate of Health)
|
|
web
|
hl7norway.github.io
|
Norwegian base profiles - principles (HL7 Norway)
|
|
web
|
hl7norway.github.io
|
Identifier in FHIR (HL7 Norway)
|
|
web
|
hl7norway.github.io
|
HER-id and FHIR (HL7 Norway)
|
|
web
|
www.helsedirektoratet.no
|
Registering health and care data (Norwegian Directorate of Health)
|
|
web
|
www.helsedirektoratet.no
|
Reporting services with definitions and reporting requirements (Norwegian Directorate of Health)
|
|
web
|
www.helsedirektoratet.no
|
Functional assessment and scoring / ICF (Norwegian Directorate of Health)
|
|
web
|
www.helsedirektoratet.no
|
ICPC-2 (Norwegian Directorate of Health)
|
|
web
|
utviklerportal.nhn.no
|
Welfare Technology Hub, VKP (NHN)
|
|
web
|
utviklerportal.nhn.no
|
Patient's measurement data (NHN Developer Portal)
|
|
web
|
utviklerportal.nhn.no
|
VKP and Patient's measurement data (NHN Developer Portal)
|
|
web
|
utviklerportal.nhn.no
|
Municipal interoperability services (NHN Developer Portal)
|
|
web
|
github.com
|
Oslo municipality: Patient Journal API
|
|
web
|
github.com
|
Oslo municipality: Encounter profile
|
|
web
|
github.com
|
Oslo municipality: CarePlan profile
|
|
web
|
utviklerportal.nhn.no
|
This IG does not replace or override VKP
or Patient's measurement data (PMD)
. VKP and PMD describe specific handling, collection and availability of measurement data, including detailed use of Observation
for relevant measurement types. This use case only shows how measurements may be included as supporting data in a broader municipal follow-up context together with no-kommune-EpisodeOfCare
, no-kommune-CarePlan
and no-kommune-Encounter
.
|
|
web
|
utviklerportal.nhn.no
|
This IG does not replace or override VKP
or Patient's measurement data (PMD)
. VKP and PMD describe specific handling, collection and availability of measurement data, including detailed use of Observation
for relevant measurement types. This use case only shows how measurements may be included as supporting data in a broader municipal follow-up context together with no-kommune-EpisodeOfCare
, no-kommune-CarePlan
and no-kommune-Encounter
.
|
