A hospital buys a product per job: wayfinding, staff comms, room booking, video walls. Each is a vendor, a renewal and a box on the wall. This is one device where the job is configuration.
Every system in this category is a content manager with a media player attached. Somebody builds a slide, somebody schedules it, the screen plays it back, and the work never stops. That is why the clinic list is six weeks old and the lift notice is from March. Ava reads what the hospital already knows, and the screens follow it.
One runtime, one build, one update. What a screen IS at any moment is data, not a separate product you bought. Everywhere else, each of these is a different vendor with its own renewal and its own box on the wall.
None of the screens above is a slide. Each is a view of something the hospital already maintains: the queue system, the room calendar, the campaign schedule, the estates notices. If a system has an API, a feed, an export or a page you already publish, it can drive a screen.
That is the whole difference. A content manager asks somebody to keep hundreds of screens current. This asks the systems that already know.
Video is not a compromise here. Full HD at 30 frames per second plays across the whole estate at once, because the file is cached on every device in advance and played locally rather than streamed to each screen at the moment it matters.
The hardware was chosen with headroom rather than to a price. Multiple simultaneous HD video feeds were tested on the chip before a single unit was ordered, because a device you cannot ask more of later is a device you replace.
Scan the code on the screen and present from your seat, in a consult room, a teaching room or an MDT meeting. No cable, no adapter, and no walking a visiting consultant through your wifi. How casting works →
One message takes every screen on every campus at once, in priority order, and nothing outranks it. It goes out from a phone and clears the same way. This is what most screen systems do slowest, because signage was designed around scheduling rather than interruption.
Every device reports its own condition continuously, so you hear it from us rather than from somebody standing in front of it.
Ticket numbers, room schedules and campaign slots need no record about a patient, and the product holds none, which shortens the review because there is nothing to review. What we do not do: patient room boards showing a name, a condition or a care team, and anything reading from a clinical record system. Those are real products and they are not this one.