Decentralized Competences SSR

Decentralized competences can be added to the infrastructure as a service request, so that when configured and assigned to clinicians from their regional and municipal IDPs, the competences can be processed (carried in the session tokens and persisted on the Practitioner resource) on the infrastructure.

Adding support for new decentralized competences requires some terminology updates. For each decentralized competence, the infrastructure must know the value Keycloak will be receiving from the IDPs as well as a code value used internally in the eHealth Infrastructure. The code value is the code that will be stored on the Practitioner resource as a Practitioner.qualification.

The requester can either ask for the new codes to be added to the existing CodeSystems:

• Practitioner Competences - eHealth Infrastructure

• OIO-BPP Competences - eHealth Infrastructure

or, the request can request having new CodeSystems created for their own managed competences.

Required Input from Request

Using existing CodeSystem we need the following information:

• Code and display value for internal use on the eHealth Infrastructure (coded value used in the Practitioner resource).

• Code and display value for the competence as it will be received on Keycloak (the value assigned by the clinicians IDP)

• Urgency, whether the competence support is needed immediately, or if it can wait for the next release.

Requiring new CodeSystems we need same information as above, and additionally the following information for values needed to define the CodeSystem(s) (see Wound types - JSON Representation - eHealth Infrastructure for inspiration as a CodeSystem owned by Region North):

• CodeSystem url

• CodeSystem name (cannot contain spaces or special characters, only letters and numbers)

• CodeSystem title

• CodeSystem description

If new CodeSystems are requested for both the received value and the internal code, the requester must supply the CodeSystem attributes for each of the two CodeSystems.

Time estimate

• Standard delivery (the next release) - 3 hours

• Expedited (updated on environments asap - Requires explicit approval from FUT-S since it requires Keycloak configuration) - 2 hour baseline + 1 hour per environment