...

• Technical Infrastructure - this is the compute, networking and storage part.

• Platform - this is Kubernetes, internal databases and more

• Platform cross-cutting concerns:

  • Security

  • Logging

  • Deployment Model

  • Messaging

• eHealth Infrastructure - the servicesServices

• Backend-for-frontend (BFF) -

  • eHealth Application BFF - backend for application provided with the eHealth Infrastructure, see eHealth Applications.

  • Solution Application BFF - a vendor providing a Telemedicine solution application may choose to add an own backend that consumes the eHealth Infrastructure services whilst providing own API towards the application client. The vendor may choose to let the application consume eHealth services directly or use a hybrid between BFF and direct invocation.

• Application Client/Service - it is expected that applications/services (Danish: fagsystemer) used by healthcare providers, social providers or social care providers will consume eHealth Infrastructure services directly, but they, too, may choose to use a BFF.

Domains

Overall, the services of the eHealth Infrastructure are divided into three domains elaborated in the following.

...