Standard Architecture
The BlueKee CAF deployment uses the following architectural elements from the CAF:
Architecture Element | Used | Provider |
---|---|---|
Database | ✅ | Percona MySQL (Azure Kubernetes Service) |
Mobile | ✅ | React Native |
Portal | ✅ | Azure Kubernetes Service |
Microservices | ✅ | Azure Kubernetes Service |
Storage | ✅ | Azure Storage Accounts |
Identity | ✅ | Azure Active Directory B2C |
Redis | ✅ | Azure Redis Cache |
Application Gateway | ✅ | Azure Application Gateway |
Vault | ✅ | Azure 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