Background
There are periodic imports of organisational Periodically, the eHealth Infrastructure imports data from two sources: the KOMBIT Support System (STS, Da: Støttesystem) Organisation Organization and the national National Health Organisation Organization Registry (Da: Sundhedsvæsenets Organisationsregister, SOR). To be able to traverse from municipal FHIR Organization in eHealth to the SOR-imported counterpart, a relationship between the two must be established. The current registering in KOMBIT STS Organisation and SOR does not support this relationship being automatically maintained in eHealth. Therefore it is possible for the customer to .
See Automated Processing for when the import is performed.
For organizations in eHealth Infrastructure with their imported counterparts from KOMBIT STS Organisation and SOR, a relationship must be established.
This connection isn't automatically created in eHealth, so customers must provide these connections themselves. Therefore, the customer must provide these mappings.
Request load
A load of relationships can be requested by creating To request these relationships, customers must create a service request in Cherwell with the following informationdetails:
The environment (production, preproduction, external test etc.) where the relationships should be loaded.
An attached CSV file
...
that specifies the relationships.
Format
The
...
organization relationship file is
...
in CSV format with no header, and
...
semicolons are used as field
...
separators.
...
Each line in the file defines a relationship and
...
has this structure:
| Code Block | ||
|---|---|---|
| ||
<STS Organization Type>;<STS Organization Identifier>;<SOR Identifier> |
...
(KOMBIT) STS Organization Type is one of “ORG” and “ORG-UNIT”
...
Whether to provide new file(s) or maintain and provide continuously growing file(s) is up to the customer.
...
Organisation relationship file(s) are processed as updates (with searches to check if already added).
...
If removal of relationship is required, please state this in the service request (as removal is not supported through the organisation relationship file)
Environments
...
<STS Organization Type>can be either "ORG" or "ORG-UNIT"
Customers can choose to provide new files or continuously update existing ones. These files are processed as updates, and a search is conducted to prevent duplicates.
If the customer needs to remove a relationship, please mention it in the service request, as removal isn't supported through the organization relationship file.
Environments
For all test environments (except production), the same relationship mapping can be used because they share both SOR test organizations and STS test organizations.
A However, a different relationship mapping is needed required for the production environment since STS organizations can be different in this environment. setting (SOR organizations are identicalremain the same).