CH UMZH Connect IG (R4), published by UMZH. This guide is not an authorized publication; it is the continuous build for version 1.0.0-cibuild built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/umzhconnect/umzhconnect-ig/ and changes regularly. See the Directory of published versions

Registry

Registry

All participating organizations — both Placers and Fulfillers — are registered in a shared UMZH-Connect Registry, inspired by IHE mCSD (Mobile Care Services Discovery). The registry serves as a directory for discovering participating organizations, the services they offer, and their FHIR API endpoints.

The registry comprises three interrelated resource types:

• Organization — a participating healthcare provider (Placer or Fulfiller)
• Endpoint — the FHIR REST API endpoint of an organization, linked via Organization.endpoint
• HealthcareService — a specific service offered by an organization, linked to the organization via HealthcareService.providedBy

classDiagram
    direction LR
    Organization "0..*" --> "0..*" Endpoint : endpoint
    HealthcareService "0..*" --> "0..1" Organization : providedBy

Because the registry is a shared, cross-organizational system, all references to registry-hosted resources must use absolute URLs (e.g. http://registry.example.org/fhir/Organization/Fulfiller). Consequently, any reference to a registry-hosted Organization must use an absolute URL — for example Task.owner, Task.requester, and PractitionerRole.organization (e.g. as used in ServiceRequest.requester) — rather than pointing to the local FHIR server of the Placer or Fulfiller.