Non-normative example of minimum search and read capabilities for a municipal FHIR server following this IG (v0.3.0). Implementations SHOULD publish their own CapabilityStatement reflecting actual support.

Municipal plan profile for follow-up, goals, interventions and planned activity in health and care services. The profile is used when a system needs to share a plan that shows what the municipality follows up, which goals or interventions are relevant, and which activities are planned or completed. The plan can point to requests, planned appointments, completed contacts, observations, supporting documents, goals and responsible team.

Municipal contact profile for an actual completed contact, assessment, meeting, visit or stay in municipal health and care services. The profile is used when a system needs to share that a municipal contact has taken place, and provides a shared minimum for patient, timing, contact form, responsible unit, participants and location. The contact can be linked to a municipal episode through episodeOfCare, to a request through basedOn, and to a planned appointment through appointment when the contact fulfills a previously shared Appointment.

Municipal episode profile for collecting follow-up over time when the municipality has a responsibility, service context or coordinated follow-up process. The profile is used as shared context for requests, plans and completed contacts that belong to the same municipal follow-up. It provides a shared minimum for patient, status, period, responsible organization, relevant requests and optionally team or care manager.

Municipal request profile for a referral, assignment or order that should be followed up by a municipal health and care service. The profile is used when a system needs to share what the municipality should do or follow up for a patient, for example home nursing, practical assistance, rehabilitation or digital follow-up. It provides a shared minimum for requested service, patient, requester, requested performer, timing/period and relevant basis. Decisions, assessments and other supporting documents can be linked to the request through reasonReference or supportingInfo.

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.

Identifier system for Norwegian organization numbers from Enhetsregisteret. Used by no-basis Organization.identifier:ENH.

Non-normative example of a decision document

Non-normative example of an evaluation contact in the same episode

Non-normative example of a follow-up contact in the same episode

Non-normative example of a follow-up goal

Non-normative example of a health concern relevant for municipal follow-up

Non-normative example of a municipal contact

Non-normative example of a municipal episode

Non-normative example of planned municipal follow-up

Non-normative example of a municipal service unit

Non-normative example of next of kin in municipal follow-up

Non-normative example of a structured assessment

Non-normative example of an occupational therapist in the municipality

Non-normative example of an occupational therapist role in municipal follow-up

Non-normative example for municipal use

Non-normative example of a location for home visits

Non-normative example of a phone contact in the same episode

Non-normative example of a physiotherapist in the municipality

Non-normative example of a physiotherapist role in municipal follow-up

Non-normative example of a planned municipal follow-up visit

Non-normative example of a second municipal request in the same episode

Non-normative example of a role in a municipal service

Non-normative example of a municipal location

Non-normative example of a municipal practitioner

Non-normative example of a request for a municipal service

Non-normative example of a municipal short-term stay represented as an Encounter

Non-normative example of a municipal short-term stay location

Non-normative example of a multidisciplinary municipal team

Fictional example that records absence of a result, not a completed KPR functional assessment.

Fictional KPR functional assessment with domain, scale, identity, time and responsible organization.

Fictional historical record. Score 9 in 9165 is inactive from 1 January 2026.

Fictional KPR functional assessment with domain, scale, identity, time and responsible organization.

Fictional KPR functional assessment with domain, scale, identity, time and responsible organization.

Fictional KPR functional assessment with domain, scale, identity, time and responsible organization.

Fictional KPR functional assessment with domain, scale, identity, time and responsible organization.

Fictional KPR functional assessment with domain, scale, identity, time and responsible organization.

Groups assessment and follow-up in August. The episode type remains text because the episode is broader than one service code.

Observations reference the contact through Observation.encounter. The contact references the municipal episode.

An individual goal with reassessment to support evaluation. A score alone does not determine goal achievement.

Plan shown after the 31 August review. Initial assessments remain the basis, while reassessment is linked as an activity outcome.

Observations reference the contact through Observation.encounter. The contact references the municipal episode.

Home nursing request where the personal hygiene assessment justifies the request and other relevant functional assessments provide supporting information.