...
| Gliffy | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Starting from the bottom of the figure, the system contains:
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 Services - The eHealth services exposed to third party for developing Telemedicine Solutions.
eHealth Applications - End user application provided as part of the eHealth Infrastructure.
Telemedicine Solutions - End user application provided by third party.
Backend-for-frontend (BFF) - Design Pattern for rather than having a general-purpose API backend, a BFF expose a specialized backend per user experiences.
eHealth Application BFF - backend backends for application provided with the eHealth Infrastructure, see eHealth Applications.
Solution Application BFF - a vendor providing a Telemedicine solution 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.
...