Healthcare IT Infrastructure

A machine that fails does not stop patients from arriving. Appointments, documentation and data exchange over the telematics infrastructure carry on, or they do not. What was needed was a server environment the specialist applications of the German healthcare system can rely on: the connection to the telematics infrastructure, DAKOTA for certificate-based encrypted data exchange, and the patient documentation software.

Building and running the server environment, from the machine up to the services on it. Alongside that came the rollout of a workspace and cloud system for everyday work, meaning accounts, file storage and access rights.

Proxmox is the base layer. The services run separately in virtual machines and containers rather than sharing one box. Linux where Linux is the better choice, Windows where the specialist application insists on it, and in German healthcare it insists more often than anyone would like.

Separate machines mean separate failures. An update to the documentation software cannot drag the telematics connection down with it, and every machine can be backed up and restored on its own. The workspace and cloud system sits beside that, not on top of it: working files and communication live there, while the specialist applications stay in their own walled-off environment.

The client is not named here, and that is not coyness. Anyone running systems in German healthcare works on environments that process health data, which are special categories of personal data under Article 9 GDPR. The names of practices, care services and institutions do not belong in a reference list without explicit clearance. We name what was built, not who it was built for.

The environment is running. Telematics infrastructure, DAKOTA and patient documentation are connected, and the workspace and cloud system is in service. We do not measure downtime or processing time in this setup, so no figures are claimed here.