/
Adding new vendor

Adding new vendor

For a new vendor to get access to the FUT environments please contact FUT-S Contact Information .

When a new vendor get access to an environment they will be able to:

  • Get access to the requested environment

  • Be able to deploy to the system

  • Get access to monitoring tool (SPLUNK)

  • connect with the requested Client-ID

  • Get access to Systematic thru Cherwell

 

All requested user will receive a mail with credentials to the environment and another for Cherwell.

To get access contact FUT-S Contact Information

Keycloak - application-facing

Client registration on the application-facing Keycloak instance. The vendor supplies the client-id's. Client(s) must be registrered pr. environment. For each client-id the vendor must supply the following:

  • Targeted citizen or clinician use

    • If clinician use, are test users used?

  • List of redirect urls

    • Do NOT supply wildcard URL’s. They will not be accepted.

  • List of required Coexistence scopes

 

FUT-I Configuration

Co-existence tag

FUT-S manages the governance of coexistence tags and issues the non-value-bearing keys to user systems upon request from projects. The projects determine, in collaboration with FUT-S, whether there should be separate coexistence tags for the project's employee and citizen solutions respectively, or whether they should be regarded as a user system complex and share a coexistence tag.

When approved, add the new co-existence to the following CodeSystem : https://ehealth.sundhed.dk/fhir/CodeSystem-ehealth-system.html . The relevant ValueSet includes all codes from the CodeSystem. If adding directly to environments, remember to add to the GitHub Implementation Guide repository afterwards.

 

eHealth-program

Add the new program to the following CodeSystem https://ehealth.sundhed.dk/fhir/CodeSystem-ehealth-program.html. The vendor should provide the neccesary values. The relevant ValueSet includes all codes from the CodeSystem. If adding directly to environments, remember to add to the GitHub Implementation Guide repository afterwards.

 

Treatment areas

The coexistence scope configured in Adding new vendor is used to limit vendor solutions to Treatment Areas (specific conditions codes).

The vendor must define treatment areas which are relevant for the solution. See the following example for collection of treatment areas for KPRO;: https://build.fhir.org/ig/fut-infrastructure/implementation-guide/branches/release_2026.1/ValueSet-ehealth-treatment-areas-xb.html. The creation of these should be handled as a service request, which can be requested through the Service Desk ( Contact Information ).

 

If a new user need access after the vendor access is added please contact FUT-S Contact Information