Managing and Using Organization, CareTeam and Practitioner
Summary
This page explains how organizational data—particularly related to municipalities, regions, and general practitioners—is managed and utilized within the eHealth Infrastructure.
It highlights the dual origin of organizational records from national registries like SOR and FK-ORG, and describes how these records are used in clinical contexts, audit logging, and document sharing. The page also outlines the manual processes required to reconcile duplicate entries and maintain accurate relationships between organizations.
Sub pages
Origin and Use of Organization
Most FHIR Organizations in the eHealth Infrastructure are automatically created and updated as described in Importing and updating Organization information from SOR and FK-Organisation into eHealth Infrastructure.
Most organisations, including municipal ones, are imported from the Health Organisation Registry (SOR). However, municipal organisations also have a separate FHIR Organization resources created when of importing from the municipal KOMBIT system FK-ORG.
This dual import process can result in duplicate FHIR organisations for municipal organisations, depending on how they are registered in SOR and FK-ORG.
The different types of organisations and their use are shown in the table below.
Type | Origin | Use |
|---|---|---|
Regional | SOR | General use |
General Practitioner | SOR | General use |
Municipal | SOR | In CDA documents and preferred in audit logging (registering of Practitioner’s actions and access to Patient data) to MinLog2 - see Architecture and Domains (see explanation below). |
Other | SOR | General use |
Municipal | FK Organiation | General, but not directly in CDA documents (see explanation below) |
General use includes:
login and security context
managing organization in CareTeam
modifier-role (owner, co-author) and in the intended audience of plan definitions and/or questionnaire
assigning managing organization for episodes of care
transformations to/from CDA documents (see Behind the Scenes )
As will be apparent on subpages, the described duality in origin must be taken into account when finding and using Organization.
Using of Municipal Organisations from SOR
A municipal employee (Practitioner) use the eHealth Infrastructure within a municipal organisational context. This context is designates a municipal-type organisation orinating from FK-ORG.
CDA document Archiving.
When Patient data is archived as a CDA document in the national document sharing infrastructure, see Behind the Scenes, the municipal organisation must be identified using its SOR identifier. Therefore, CDA document assembly requires mapping from a municipal organisation with FK-ORG origin to its corresponding organisation with SOR origin.
Audit logging.
When municipal employees (Practitioner) create, modifies or accesses patient data, the infrastructure automatically logs the actions in the national MinLog2 service. This enables citizen to see which employee has accessed their data, for instance, through the citizen portal sundhed.dk. The audit logging prefers organisational context identified by the SOR identifier.
Establishing Relations
Both use cases require establishing a relation between the municipal organisation from FK-ORG and its counterpart from SOR. This process is described in Load relationships between organisations imported from KOMBIT STS Organisation and SOR.