On-premises monitoring for medical gas, UPS, and critical environment systems across hospital sites. Patient environment data processed entirely within the hospital network satisfies GDPR Article 9 health data requirements without a complex data processing framework.
Hospital facilities teams monitor critical systems — medical gas manifolds, oxygen pressure, vacuum, UPS battery health, temperature in pharmacy cold stores, sterile environment pressure differentials — that are directly linked to patient safety. Some of these data points, when combined with ward location and timestamp, constitute health data under GDPR Article 9. Sending them to a cloud analytics platform creates a special category data transfer that requires explicit legal basis.
BunkerM Enterprise runs on a server within the hospital's private network. Siemens Desigo CC BMS, Schneider APC UPS systems, and Modbus-connected medical gas analysers publish Sparkplug B metrics. The facilities team queries live status: "What is the oxygen pressure on Ward 4 right now?", "Which UPS units are below 80% battery health?", or "Are all pharmacy cold stores within range?" All queries and responses are processed locally.
A hospital group with 8 sites deploys BunkerM Enterprise at its central facilities management office, connected to all sites over the group's private network. Medical gas, UPS, and environment data from each site is aggregated into a single broker instance. The on-call engineer receives Telegram alerts for critical alarms. Patient environment telemetry — temperature, pressure, gas levels linked to ward locations — never leaves the hospital group's private network.
🔒 GDPR Article 9 health data stays on-premises. Environmental data linked to patient ward locations constitutes special category health data under GDPR Article 9. Processing it locally on the hospital's own infrastructure removes the requirement for a legal basis for transfer to a third-party processor. BunkerM Enterprise does not transmit any data outside the hospital network.