Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

Introduction

The eHealth Infrastructure performs 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 on a daily basis.

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:

  1. 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 identifiers 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.

  2. 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 exclude 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.

Data mapping from SOR data to FHIR Organization of profile ehealth-organization:

  • The SOR identifier is stored as an Organization.identifier with the system 'urn:oid:1.2.208.176.1.1'.

  • If the SOR organization has a CVR number the is stored as in the Organization.cvrNumber element.

  • Relationships defining the organization trees are reflected in the Organization.partOf element.

  • VirtualAddressInformation is stored as ContactPoints under the Organization.telecom element.

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 either udførende or ansvarlig.

  • 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

https://prod.serviceplatformen.dk/service/Organisation

Non-production (e.g. EXTTEST)

For fewer municipalities (at time of writing)

TEST

https://exttest.serviceplatformen.dk/service/Organisation

Organization discovery

For each municipality, the import starts by

  1. Search for all OrganisationEnhed having the KLE code ‘29.70.10 Telesundhed' or '29.70.20 Telemedicin' assigned as Opgaver as either udførende or ansvarlig.

  2. For all found OrganisationEnhed their parent organizational tree is found using the RelationListe.Overordnet attributes.

  3. For OrganisationEnhed not having a RelationListe.Overordnet the RelationListe.Tilhoerer attribute will be used to retrieve the Organisation.

  4. Then the Virksomhed is referenced by the Organisation's RelationList.Virksomhed attribute will be retrieved.

  5. Lastly, the referenced addresses will be retrieved from the Adresser service and Danish Adresse Register (DAR).

  6. 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 ehealth-organization:

  • The Organisation identifier is stored as an Organization.identifier with system 'https://www.kombit.dk/sts/organisation'.

  • The OrganisationEnhed identifier is stored as an Organization.identifier with system 'https://www.kombit.dk/sts/organisation'.

  • The CVR Number defined on the Virksomhed is copied to all children in the organizational tree.

  • Relationships defining the organization trees are reflected in the Organization.partOf element.

  • (upcoming functionality) Address: Adresse resources with Rolle 'SOR-ID' a relationship to the related SOR organization is reflected in the Organization.relatedTo element.

  • Telecom: Adresse resources with Rolle 'Email' or 'Telefon' are stored as ContactPoints under the organization.telecom element.

  • Address: Adresse resources with Rolle 'Postadresse' are stored as Organization.address.

In case resolution of 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:

  1. The customers provide mapping as MS Excel files to the Systematic AO team, which then triggers the relationship being created or

  2. 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.

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 identifiers 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.

  • No labels