Hospital Network Ties Infrastructure Health to Care Continuity With Ollandi
A multi-site hospital network uses Ollandi to understand infrastructure through its effect on care: which wards, departments and clinical systems are exposed when a server, link or identity service fails.
The condition
The network operates several hospitals and outpatient clinics on shared infrastructure. Patient records, laboratory systems, imaging and pharmacy all depend on the same data centre, the same identity service and the same links between sites.
The IT team measured health in technical terms: CPU, link utilisation, disk latency. Clinical leaders needed something different. When a server slowed down, they wanted to know whether the emergency department could still pull patient histories and whether imaging results would reach the wards. Nobody could answer quickly.
Ollandi's role
The network deployed Ollandi under the Observe & Notify control. Ollandi reasons over infrastructure telemetry, identity events and network state, and maps each component to the clinical services and sites that depend on it. It does not read clinical records.
Care continuity as the measure
When a component degrades, Ollandi reports its consequence for care: which hospital, which department and which clinical system is affected, and whether staff have a working alternative. The IT team still sees the technical detail. Clinical leadership sees what it means for patients.
Identity threats in a clinical setting
Shared workstations and frequent shift changes make identity activity noisy in hospitals. Ollandi separates normal shift patterns from access that does not fit, such as a clinical account querying systems at a site where its owner does not work, and raises those cases with the evidence for review.
Care leadership keeps command
Any action that could interrupt clinical work is a decision for the people responsible for care. Ollandi explains and recommends. It does not change infrastructure on its own authority.
The operating outcome
Incidents are now described in terms clinical leaders can act on, and the IT team prioritises repairs by their effect on patients rather than by the order alerts arrived. Suspicious identity activity is investigated with its context attached instead of being lost in shift-change noise.
Operating control: Observe & Notify.
