...
Whenever a client manipulates (anything but read operations) a video appointment in the eHealth Infrastructure the microservice responsible for wrapping the VDX endpoint is invoked and communicates with the VDX endpoint. As such, it is transparent of the clients of the eHealth Infrastructure that they communicate with the actual VDX endpoint. This also means that the eHealth Infrastructure acts as a cache for the VDX endpoint which in turn means that the security model for accessing video appointments is governed by the rules listed on Tokens, roles Roles and RBAC/ABAC (the ruleset for accessing video appointments follows the same rules as for regular appointments).
The video meeting itself is hosted and served by the VDX service and not the eHealth Infrastructure