Introduction
The eHealth Infrastructure performs the import of organizations information from Sundhedsvæsnets Organisationsregister (SOR) and KOMBIT Fælleskommunalt (FK) Organisation (formerly Støttesystemet Organisation (STS-ORG)) to the eHealth Infrastructure daily.During the import new or updated information in SOR and FK Organisation is updated in the eHealth Infrastructure.
A relationship between the FK Organization and the SOR-imported counterpart must be established.
This relationship can be established in two ways:
The customers provide mapping as MS Excel files to the Systematic AO team, which then triggers the relationship being created.
The customer provides organisation relationship file(s) containing mappings between KOMBIT STS Organization and SOR identifiers. This input is provided to an operation in the eHealth system by SRE. The operation will then process the file line-by-line and establish the relevant related-to relationships in the FHIR Organization resources.FUT Infrastructure automatically creates the relationship during import from FK Organisation if the SOR code is available in FK Organisation.
The Municipalities FK Organisation administrator registers the SOR kode in the FK Organisation system (as address of type SOR ID), and the FUT infrastructure will automatically create the relationship during import.
eHealth Infrastructure imports from Sundhedsvæsnets Organisationsregister (SOR)
The eHealth Infrastructure imports organization information from Sundhedsvæsnets Organisationsregister (SOR) every night approximately 1 hour after SOR publishes the daily data file.
See Automated Processing for when the import is performed.
The SOR data file contains all organizations in SOR. The data file is published at http://filer.nsi.dk/sor/data/sor/sorxml/v_2_0_0/Sor.zip
and is used in all FUT environments (exttest, test002 (education), pre-prod, production).
The import excludes the organization tree below 'Sundhedsdatastyrelsen' (SOR Identifier 634491000016008), and all children found below the organization.
All non-excluded InstitutionOwner, HealthInstitution and OrganizationalUnit resources found in the data file are transformed into eHealth Organization resources and imported.
Data mapping overview
The import respects the address inheritance rules defined by SOR by copying the relevant addresses from parents if not available for the current organization.
The import does not copy other attributes and values from the parent, and the current organizations are imported as-is.
The following table explains how each of the attributes on the FHIR resource is mapped from the SOR data model.
See https://ehealth.sundhed.dk/fhir/StructureDefinition-ehealth-organization.html for the eHealth FHIR Organization profile.
See https://www.nspop.dk/display/public/web/SORUS+-+Guide+til+anvendere for a description of SOR data.
ehealth-organization element | Source from SOR | Description |
---|---|---|
| N/A | Generated by FHIR server |
| N/A | Generated by FHIR server |
| N/A | |
| N/A | |
| N/A | |
| N/A | |
| N/A | |
| N/A | |
| Always set to | |
| N/A | |
| always set to | |
|
| The SOR identifier is stored in eHealth Infrastructure |
|
| |
|
| |
| N/A | |
| Computed based on | Set to true when: sor1:ToDate is not set or is in the future and sor1:FirstFromDate is not a future date. Set to false when sor1:ToDate is in the past or sor1:FirstFromDate is a future date. We will be using FirstFromDate as this is the flag used in SOR to set organizations active - FromDate is set when other data on the organization changes. |
|
| |
|
| |
| Concatenation of | Example: For SorIdentifier=914571000016002 with the name "KOL Klinik" the constructed alias will be: "Region Midtjylland, Aarhus Universitetshospital, Lungesygdomme, Lungesygdomme Klinik, KOL Klinik" |
|
| If the SOR organization has a CVR number, it is stored. Only if available on the current SOR entity. (no inheritance) |
| Always set to SOR. See Organization Source - eHealth Infrastructure v3.0.0 (sundhed.dk) | |
| Calculated from | Relationships defining the organization trees are reflected in the FHIR id for the parent organization according to the SOR hierarchy. |
|
| |
| Code calculated from
| Stored as ContactPoints See https://hl7.org/fhir/R4/valueset-contact-point-system.html If not present on the current element the VirtualAddressInformation is inherited from the SOR parent. |
| Two addresses will be stored in FHIR.
And either an
|
Then a prioritized select of http://filer.sst.dk/sor/docs/sorxml/v_2_0_0/SorXmlDocumentationV2.html describes the inheritance of addresses in the SOR structure (translated to English):
After applying the inheritance logic the values are copied to the FHIR model. Ie. addresses are not left blank in the FHIR model. |
|
| |
|
| |
| Either a | |
| N/A | Not created during import. |
|
| |
|
| |
|
| Translates to the Danish 'Ydernummer' |
|
|
eHealth Infrastructure imports from KOMBIT Fælleskommunalt (FK) Organisation
The eHealth Infrastructure imports organization information from the FK Organisation every night around midnight.
For the import to be performed a Service Agreement in KOMBIT Serviceplatform must be established per municipality.
The import performs the following:
Process all 98 municipalities given they have a Service Agreement.
For OrganisationEnhed to be imported they must have the KLE code ‘
29.70.10 Telesundhed
' or '29.70.20 Telemedicin
' assigned as Opgaver as eitherudførende
oransvarlig
.Import and update information from each municipality individually
eHealth Environment | Service Agreements in place | KOMBIT Environment imported from | FK Organisation Service |
---|---|---|---|
Production | For all municipalities | PROD |
|
Non-production (e.g. EXTTEST) | For fewer municipalities (at the time of writing) | TEST |
|
Organization discovery
For each municipality, the import starts by
Search for all OrganisationEnhed having the KLE code ‘
29.70.10 Telesundhed
' or'29.70.20 Telemedicin
' assigned as Opgaver as eitherudførende
oransvarlig
.For all found OrganisationEnhed their parent organizational tree is found using the
RelationListe.Overordnet
attributes.For OrganisationEnhed not having a RelationListe.Overordnet the RelationListe.Tilhoerer attribute will be used to retrieve the Organisation.
Then the Virksomhed is referenced by the Organisation's RelationList.Virksomhed attribute will be retrieved.
Lastly, the referenced addresses will be retrieved from the Adresser service and Danish Adresse Register (DAR).
The found Organisation and OrganisationEnhed resources are transformed into eHealth Organization resources and imported.
Data mapping overview
Data mapping from FK Organisation objects to FHIR Organization of profile https://ehealth.sundhed.dk/fhir/StructureDefinition-ehealth-organization.html :
The following table explains how each of the attributes on the FHIR resource is mapped from the FK Organisation data model
ehealth-organization element | FK Organisation Source | Comment |
---|---|---|
| Generated by FHIR server | |
| Generated by FHIR server | |
| N/A | |
| N/A | |
| N/A | |
| N/A | |
| N/A | |
|
| A relation to corresponding FHIR Organisations with the given SOR Id is established. Adresse resources with Rolle ' |
| N/A | |
| Always set to | |
| Not used | |
| For FK Organisation always | |
| If Organisation | |
| If Organisation | |
| if Organisation | |
| Not used | |
|
| See https://ehealth.sundhed.dk/fhir/CodeSystem-ehealth-oio-organization-type.html |
| If Organisation | Has to be Aktiv for active to be true. If value is “Inaktiv”, then active is set to false. |
| Organisation | |
| Concatenation of 'name' from the top of the tree down to and including the current entity. | |
| OrganisationEnhed.Overordnet .. or if Overordnet isn't set: OrganisationEnhed.Tilhoerer | Relationships defined in the organization trees from FK Organisation are reflected in the FHIR id for the parent organization according to the OIO hierarchy. |
| The first found entry in | Address: Adresse resources with Rolle ' |
| Always | In case of a STS ORG Adresse |
| Always | In case of a STS ORG Adresse |
| From Adresse service
| In case of a STS ORG Adresse |
| From Organisation|OrganisationEnhed service
| In case of a STS ORG Adresse |
| From Organisation|OrganisationEnhed service
| In case of a STS ORG Adresse |
| Always | In case of a DAR address |
| Always | In case of a DAR address |
|
| In case of a DAR address |
|
| In case of a DAR address |
|
| In case of a DAR address |
| Always | In case of a DAR address |
|
| In case of a DAR address |
|
| In case of a DAR address |
| The first found entries in | Telecom: Adresse resources with Rolle 'Email' or 'Telefon' are stored as ContactPoints under the |
| Always " | |
| " | |
| From Adresse service
| |
| From Organisation|OrganisationEnhed service
| |
| From Organisation|OrganisationEnhed service
| |
| Not set by import | |
|
| |
|
| The CVR Number defined on the Virksomhed is copied to all children in the organizational tree. This CVR number is taken from the Organisation-associated Virksomheds object and applied to all Organisation and OrganisationEnhed in the tree. The top-level Organisation in a hierarchy is accessed with the "tilhører" relation in an OrganisationEnhed |
| Not available in FK Org. | This information does not exist for address in OIO Organisation (Adresse). RegionCode for addresses is read from DAR: |
| Not available in FK Org. | This information does not exist for address in OIO Organisation (Adresse). Municipality code for addresses is read from DAR: |
| Not available in FK Org. | |
| Not available in FK Org. |
In case the resolution of the Address and telecom fails, it is logged and processing continues. This leaves the Address and telecom unchanged.
Establish the relationship between the FHIR Organization and the SOR-imported counterpart
A relationship between the municipal FHIR Organization and the SOR-imported counterpart must be established.
This relationship can be established in two ways:
The customers provide mapping as MS Excel files to the Systematic AO team, which then triggers the relationship being created or
FUT Infrastructure automatically creates the relationship during import from FK Organisation if the SOR code is available in FK Organisation.
FUT Infrastructure automatically establish the relationship during import from FK Organisation
If the SOR code is available in the FK Organisation, the Municipalities FK Organisation administrator registers the SOR kode in the FK Organisation system (as address of type SOR ID), and the FUT infrastructure will automatically create the relationship during import.
The Systematics AO team establishes the relationship from MS Excel files provided by the customer
The customer provides organisation relationship file(s) containing mappings between KOMBIT STS Organization and SOR identifiers. The Systematic operation team will make the eHealth then process the file line-by-line and establish the relevant related-to relationships in the FHIR Organization resources.
The process:
The municipality creates a case against support with SOR mapping.
Systematic Application Operations (AO/SRE) carry out the task of loading SOR mapping.
Systematic reports back if there are errors or successful loading of SOR mapping.