HL7 Norway
FHIR Implementation Guide for the Norwegian Municipal Sector
Shared starting point for understanding and consistent use of FHIR in municipal health and care services.
Norwegian

FHIR Implementation Guide for the Norwegian Municipal Sector
0.2.0 - ci-build NO

FHIR Implementation Guide for the Norwegian Municipal Sector - Local Development build (v0.2.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

CapabilityStatement: KommuneFHIR Minimums-CapabilityStatement (Experimental)

Official URL: https://kommune.conteir.no/CapabilityStatement/kommune-server-capabilitystatement Version: 0.2.0
Draft as of 2026-04-17 Computable Name: KommuneFHIRServerCapabilityStatement

Shows minimum search and read support for a municipal FHIR server for the prioritized main cases: discharge and follow-up, planned municipal follow-up, and service need, decision and assignment. Planned contacts can be exposed with Appointment where relevant. Measurement data from Welfare Technology Hub (VKP) and Patient's measurement data (PMD) is not defined as part of this minimum in v0.2.

Raw OpenAPI-Swagger Definition file | Download

KommuneFHIR Minimums-CapabilityStatement

  • Implementation Guide Version: 0.2.0
  • FHIR Version: 4.0.1
  • Supported Formats: json, xml
  • Published on: 2026-04-17
  • Published by: HL7 Norge

Note to Implementers: FHIR Capabilities

Any FHIR capability may be 'allowed' by the system unless explicitly marked as 'SHALL NOT'. A few items are marked as MAY in the Implementation Guide to highlight their potential relevance to the use case.

SHALL Support the Following Implementation Guides

FHIR RESTful Capabilities

Mode: server

Municipal FHIR server with minimum search and read support for prioritized municipal main cases. Full create/read/update/delete (CRUD), booking, rescheduling and documentation write-back are not requirements in v0.2. Measurement data should be described together with Welfare Technology Hub (VKP) and Patient's measurement data (PMD) where those services are used.

Security

Actual implementations SHOULD document authentication, authorization, trust framework, legal basis, logging/audit and whether HelseID, OAuth or OpenID Connect is used. FHIR references do not by themselves grant access rights to referenced resources.

Capabilities by Resource/Profile

Summary

The summary table lists the resources that are part of this configuration, and for each resource it lists:

  • The relevant profiles (if any)
  • The interactions supported by each resource (Read, Search, Update, and Create, are always shown, while VRead, Patch, Delete, History on Instance, or History on Type are only present if at least one of the resources has support for them.
  • The required, recommended, and some optional search parameters (if any).
  • The linked resources enabled for _include
  • The other resources enabled for _revinclude
  • The operations on the resource (if any)

Base System Profile
Patient
Profile Conformance
SHALL
Reference Policy

Interaction summary
  • Supports read, search-type.

Documentation

Patient. SHOULD be represented with no-basis-Patient. Searches by Norwegian national identity number or D-number SHOULD use POST [base]/Patient/_search.

Search Parameters
ConformanceParameterTypeDocumentation
SHALLidentifiertoken

Search by Norwegian national identity number or D-number using POST _search.

SHALLnamestring
 
Base System Profile
no-kommune-Encounter
Profile Conformance
SHALL
Reference Policy

Interaction summary
  • Supports read, search-type.

Search Parameters
ConformanceParameterTypeDocumentation
SHALLpatientreference
SHALLstatustoken
SHALLdatedate

Search within a date period, for example date=ge2026-01-01&date=le2026-03-31.

SHALLepisode-of-carereference
 
Base System Profile
no-kommune-EpisodeOfCare
Profile Conformance
SHALL
Reference Policy

Interaction summary
  • Supports read, search-type.

Search Parameters
ConformanceParameterTypeDocumentation
SHALLpatientreference
SHALLstatustoken
 
Base System Profile
no-kommune-CarePlan
Profile Conformance
SHALL
Reference Policy

Interaction summary
  • Supports read, search-type.

Search Parameters
ConformanceParameterTypeDocumentation
SHALLpatientreference
SHALLsubjectreference
SHALLstatustoken
 
Base System Profile
no-basis-Appointment
Profile Conformance
SHALL
Reference Policy

Interaction summary
  • Supports read, search-type.

Documentation

Planned contact. SHOULD use no-basis-Appointment where applicable. Included when planned contacts are exposed before completion; completed contacts are represented as Encounter.

Search Parameters
ConformanceParameterTypeDocumentation
SHALLpatientreference
SHALLdatedate

Search planned contacts within a date period, for example date=ge2026-01-01&date=le2026-03-31.

SHALLstatustoken
SHALLidentifiertoken
 
Base System Profile
DocumentReference
Profile Conformance
SHALL
Reference Policy

Interaction summary
  • Supports read, search-type.

Documentation

Decision or supporting document. SHOULD be represented with no-basis-DocumentReference.

Search Parameters
ConformanceParameterTypeDocumentation
SHALLsubjectreference
SHALLtypetoken

Search by document type, for example decision document using a relevant national or local code.

 
Core FHIR Resource
ServiceRequest
Reference Policy
Interaction summary
  • Supports read, search-type.

Search Parameters
ConformanceParameterTypeDocumentation
SHALLpatientreference
SHALLsubjectreference
SHALLstatustoken