A hospital is a public building, a restricted clinical unit, a pharmacy, a utility plant and a dense device network at the same time. Clinical, biomedical, facilities, security and supply risk all act on the same campus, and each one is watched by a different department on a different console.
An overnight shift at an acute care campus. Every system does exactly what it was bought to do, and every operator follows the procedure correctly.
Security monitoring raises it at low severity, since the devices are still reporting normally, and a ticket is queued for the morning.
Ticket queuedThe security operations dispatcher calls the vendor number, reaches voicemail, and enters the activity in the shift log.
Log entryEngineering confirms the branch restored cleanly and raises a work order to inspect the switch.
Work order raisedThree departments, three queues, three correct procedures. The device monitoring tool, the badge system and the plant log do not talk to each other, and nothing in the building is responsible for the line that runs through all three. At the morning huddle the three items are read out separately, if they are read out at all. The pattern was never the problem. Ownership of the pattern was.
The same six domains resolve onto every estate. This is what they are when the estate is a hospital.
Clinical and administrative systems, the biomedical device segments that carry infusion, imaging and monitoring equipment, and the control systems behind emergency power, medical gas and air handling. A controls alarm and a network alert are the same story more often than either console can tell.
The emergency department entrance, behavioral health areas, pharmacy and controlled substance storage, infant and pediatric units, and the badge record that says who was where and when. The estate has to stay open to the public and closed in specific places at the same time.
Where a rooftop or ground helipad is in use, an uncrewed aircraft on the approach path is an operational problem before it is anything else. Detection is increasingly available. What a track means alongside ground activity in the same window is the part nobody owns.
Distributor deliveries, sterile processing consumables, single-source items, and the service vendors who hold standing access to clinical equipment. Access and supply are the same exposure viewed from two directions.
A storm that cuts a feeder, a water interruption and a regional diversion notice all act on the same question, which is what this hospital can safely take tonight. Counting them as three tickets is its own failure.
Sector threat reporting, advisories that name the equipment or software already on the floor, activity at neighboring facilities and events in the surrounding community that change what arrives at the door.
The same event matters differently at the security desk, on the unit and in the executive suite. One object, delivered at each altitude, with the clock that altitude actually runs on.
What changed on the campus in the last hour, which doors and areas it touches, and what to watch for on this shift.
What it means for this unit, for staffing and for the cases already scheduled, with the converging set behind it rather than three separate calls.
Which systems and spaces are affected, what the plant and access record actually show, and which option holds while the cause is still being worked.
What is being worked across the campus or the system, what posture is recommended and why, and what the recommendation rests on if it is questioned later.
Nothing here assumes a complete estate or a rip and replace. Sources are added as adapters against a common contract, and the score states the coverage it was computed on.
Onboarding is four things, in order.
Build the asset model for the campus, down to the units, the plant and the device segments, so a signal has something to attach to. Connect what exists and state what does not. Ratify the policy: the weights, thresholds and windows that decide what outranks what, signed by a named person rather than shipped as a default. Then run it against real traffic and compare the queue to the judgment of the people who already do this work.
Where a feed does not exist, coverage is disclosed on the object instead of the gap being quietly absorbed into a number.
We walk one real convergence case from your hospital, and we name what is built, what is specified, and what is neither.