eHealth Infrastructure
3.0.0 - release

eHealth Infrastructure - Local Development build (v3.0.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

Resource Profile: ehealth-organization

Official URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-organization Version: 3.0.0
Active as of 2024-05-16 Computable Name: ehealth-organization

Introduction

An Organizations is a formally or informally recognized grouping of people or organizations formed for the purpose of achieving some form of collective action. Includes companies, institutions, corporations, departments, community groups, healthcare practice groups, etc.

Scope and Usage

In scope of the eHealth infrastructure Organizations are limited to represent organizations in the Danish healthcare system as defined by the national health organization registry, SOR, and the joint municipalities IT community (KOMBIT) Support System Organisation, STS-ORG.

From these sources Organizations are automatically imported into the eHealth infrastructure. It is not the intention that users of the infrastructure should create any other Organization resources.

For SSL supplier organizations not maintained by the SOR or STS-ORG registries, it is possible to manually create and maintain these organizations.

Identifiers

Organizations are imported into the eHealth infrastructure from SOR and STS-ORG. This means that organisations can have different identifiers depending on the source system. For some organisations (for instance SSL suppliers), organizations can use an SSL Identifier as identifier.

Identifier Systems:

  • SOR-ID: “urn:oid:1.2.208.176.1.1”
  • KOMBIT STS-ORG-ID: “https://www.kombit.dk/sts/organisation”
  • SSL Identifier: “http://ehealth.sundhed.dk/organization/ssl”

Organizations created manually are not allowed to have identifiers of types SOR-ID or KOMBIT STS-ORG-ID.

Source

The origin of an Organization is maintained in the extension organization-source which currently has the following concepts:

  • SOR for an organisation imported from SOR
  • STS-ORG for an organisation imported from STS-ORG
  • manual for a manually created organisation

Import and merge

SOR supplies a list of updates each night. These updates will be merged into the existing organisation resources in the database.

STS-ORG provides a number of webservices where the newest organisation data can be fetched.

Contact information can be edited/added both in the integration platform and in the source systems. To ensure that no information is lost during merge, each ContactPoint will be tagged with a custodian element marking which system currently maintains it. When merging information from a given source, the ContactPoint elements with a different custodian will not be affected.

Relations to other organizations

It is possible to relate Organization resources to other Organization resources using the extension element relatedTo.

The intention with this element is to relate Organizations to other Organizations imported from another source. For instance to relate Organizations imported from SOR to similar Organizations imported from STS-ORG.

Hierarchical relations between Organizations imported from the same source are expressed using the partOf element.

Semantics of a relation between organizations

Relations between Organizations which are expressed using the extension element relatedTo have uni-directional semantics.

As an example this implies at that if two representations of the exact same Organization are imported from two different sources, then both could have a relatedTo element with the other Organization as target, and a relation type of e.g. “sameAs”.

Usage:

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

This structure is derived from Organization

NameFlagsCard.TypeDescription & Constraintsdoco
.. Organization Organization
... Slices for extension 2..*ExtensionExtension
Slice: Unordered, Open by value:url
... cvrNumber 0..1stringThe organization's identification code in the Danish 'Centrale Virksomhedsregister'
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-organization-cvrNumber
... regionCode 0..1stringThe organization's region code
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-organization-regionCode
... source 1..1CodeableConceptThe organization's source
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-organization-source
Binding: Organization Source (required)
... synchronizationStatus 1..1CodeableConceptThe organization's synchronization status
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-organization-synchronizationStatus
Binding: Organization Synchronization Status (required)
... providerIdentifier 0..1stringThe organization's provider identifier
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-organization-providerIdentifier
... specialty 0..*CodeableConceptThe organization's specialty
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-organization-specialty
Binding: Organization Specialty (required)
... relatedTo 0..*(Complex)Relations to other Organizations
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-organization-relatedTo
... identifier 1..*IdentifierIdentifies this organization across multiple systems
... type 0..*CodeableConceptKind of organization
Binding: Organization Type (required)
... name 1..1stringName used for the organization
... telecom
.... value 1..1stringThe actual contact point details
... partOf 0..1Reference(ehealth-organization) {r}The organization of which this organization forms a part
... contact
.... telecom
..... extension 3..*ExtensionExtension
..... telecomValue 1..1stringThe actual contact point details (i.e. phone number or email address)
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-organization-telecomValue
..... telecomSystem 1..1CodeableConceptType of communications system required to make use of the contact point: phone | fax | email | pager | url | sms | ean | other
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-organization-telecomSystem
Binding: ContactPoint System (required)
..... telecomCustodian 1..1CodeableConceptThe custodian that maintains the contact point: SOR | ORG | MAN
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-organization-telecomCustodian
Binding: ContactPoint Custodian (required)
..... system 0..0
..... value 0..0

doco Documentation for this format

Terminology Bindings (Differential)

PathConformanceValueSetURI
Organization.typerequiredOrganizationType
http://ehealth.sundhed.dk/vs/organization-type
from this IG

 

Other representations of profile: CSV, Excel, Schematron