Client Documentation
Trier
Architecture

Standard Architecture

The BlueKee CAF deployment uses the following architectural elements from the CAF:

Architecture ElementUsedProvider
DatabasePercona MySQL (Azure Kubernetes Service)
MobileReact Native
PortalAzure Kubernetes Service
MicroservicesAzure Kubernetes Service
StorageAzure Storage Accounts
IdentityAzure Active Directory B2C
RedisAzure Redis Cache
Application GatewayAzure Application Gateway
VaultAzure Key Vault

Custom Architecture

Trier's architecture is unusual in that it is split across two seperate environments per deployment. These environments are referred to as the 'public' and 'private' environments.

  • The public environment represents the public facing services that Trier manages in it's own tenancy. It contains just the Active Directory, some functions, and a storage account. No patient data, other than name, email and/or phone is recorded in this tenancy
  • The private environment (of which there could be many) represents the environments that are contained within the respective hospitals. These contain the bulk of services and hosts all patient data