Architecture
Triage is made of three tiers:
- Tablet – the triage application used by staff at the point of care.
- Hospital web app – one instance per hospital, hosted on the hospital’s own infrastructure.
- Cloud platform – a central web application running on Kubernetes, with one cluster per region (EU and UK).
Tablet
Section titled “Tablet”The triage application runs on tablets used by hospital staff to triage patients.
- Connects only to the web app of its own hospital, over the hospital network.
- Does not talk to the cloud platform directly.
Hospital web app
Section titled “Hospital web app”Every hospital has its own dedicated instance of the web app. It is used to:
- Administer the hospital’s setup (users, tablets, configuration).
- Use Triage from a browser alongside the tablets.
It is hosted locally, inside the hospital, so that:
- Patient data stays on the hospital’s infrastructure.
- Tablets keep working over the local network even if the hospital loses its internet connection.
Each hospital web app connects to the cloud platform of its region.
Cloud platform
Section titled “Cloud platform”The central web application runs on Kubernetes. There are two independent clusters:
| Region | Serves | Nodes |
|---|---|---|
| EU | Hospitals in the EU | 3 × OVHcloud Advance-1 |
| UK | Hospitals in the UK | 3 × OVHcloud Advance-1 |
The clusters share no data. A hospital is attached to exactly one region, which keeps data within its jurisdiction (GDPR for the EU, UK GDPR for the UK).
Cluster layout
Section titled “Cluster layout”Each cluster consists of three OVHcloud Advance-1 dedicated servers. Three nodes is the minimum for a highly available control plane: etcd keeps quorum and the cluster stays operational if any single server fails.