Load relationships between organisations imported from KOMBIT STS Organisation and SOR

Background

Periodically, the eHealth Infrastructure imports data from two sources: the KOMBIT Support System (STS) Organization and the National Health Organization Registry (SOR).

See Automated Processing | AutomatedProcessing Timerbased 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

To request these relationships, customers must create a service request in Cherwell with the following details:

1. The environment (production, preproduction, external test etc.) where the relationships should be loaded.

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

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

However, a different mapping is required for the production environment since STS organizations can be different in this setting (SOR organizations remain the same).