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
Contents:
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
The following artifacts define the specific capabilities that different types of systems are expected to have in order to comply with this implementation guide. Systems conforming to this implementation guide are expected to declare conformance to one or more of the following capability statements.
| KommuneFHIR Minimums-CapabilityStatement |
Non-normative example of minimum search and read capabilities for a municipal FHIR server following this IG (v0.2). Implementations SHOULD publish their own CapabilityStatement reflecting actual support. |
These define constraints on FHIR resources for systems conforming to this implementation guide.
| no-kommune-CarePlan |
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. |
| no-kommune-Encounter |
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 |
| no-kommune-EpisodeOfCare |
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. |
| no-kommune-ServiceRequest |
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 |
These define new code systems used by systems conforming to this implementation guide.
| Technical jurisdiction code system (NO) |
Technical helper artifact for validating jurisdiction=NO in IG Publisher. This is not a domain code system for municipal information modelling. |
These define identifier and/or code system identities used by systems conforming to this implementation guide.
| NorwegianOrganizationNumberNamingSystem |
Identifier system for Norwegian organization numbers from Enhetsregisteret. Used by no-basis Organization.identifier:ENH. |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.
| Example decision document |
Non-normative example of a decision document |
| Example evaluation contact |
Non-normative example of an evaluation contact in the same episode |
| Example follow-up contact |
Non-normative example of a follow-up contact in the same episode |
| Example goal |
Non-normative example of a follow-up goal |
| Example health concern |
Non-normative example of a health concern relevant for municipal follow-up |
| Example municipal contact |
Non-normative example of a municipal contact |
| Example municipal episode |
Non-normative example of a municipal episode |
| Example municipal follow-up plan |
Non-normative example of planned municipal follow-up |
| Example municipal unit |
Non-normative example of a municipal service unit |
| Example next of kin |
Non-normative example of next of kin in municipal follow-up |
| Example observation |
Non-normative example of a structured assessment |
| Example occupational therapist |
Non-normative example of an occupational therapist in the municipality |
| Example occupational therapist role |
Non-normative example of an occupational therapist role in municipal follow-up |
| Example patient |
Non-normative example for municipal use |
| Example patient's home |
Non-normative example of a location for home visits |
| Example phone contact |
Non-normative example of a phone contact in the same episode |
| Example physiotherapist |
Non-normative example of a physiotherapist in the municipality |
| Example physiotherapist role |
Non-normative example of a physiotherapist role in municipal follow-up |
| Example planned follow-up visit |
Non-normative example of a planned municipal follow-up visit |
| Example rehabilitation service request |
Non-normative example of a second municipal request in the same episode |
| Example role |
Non-normative example of a role in a municipal service |
| Example service location |
Non-normative example of a municipal location |
| Example service practitioner |
Non-normative example of a municipal practitioner |
| Example service request |
Non-normative example of a request for a municipal service |
| Example short-term municipal stay |
Non-normative example of a municipal short-term stay represented as an Encounter |
| Example short-term ward |
Non-normative example of a municipal short-term stay location |
| Example team |
Non-normative example of a multidisciplinary municipal team |