Visitors get lost, waiting rooms are told nothing, and a corridor screen is still running a campaign that ended in the spring because keeping it current was somebody's side job.
A visitor arriving for the first time gets lost, and asks the nearest person in scrubs. A clinic runs late and the waiting room has no idea. A screen in a corridor is showing a campaign that ended in the spring, because the person who built that loop moved departments and nobody inherited it. None of that is a content problem. It is that keeping a screen current was made somebody’s side job, and it is always the first side job to go.
Here the screens render from the systems the hospital already runs, so currency is not a person’s good intentions. Clinic lists, queue state, room bookings, menus, campus events and the emergency takeover all come from where they already live, and every screen reports whether it is actually rendering rather than whether a command was sent.
A single build and a single update path across the estate. A screen's role is configuration rather than a separate product, procurement and renewal. The profiles below are the same device under different configuration.
Each profile above is a rendered view of an existing source: queue management, room booking, campaign scheduling, estates notices. Any system exposing an API, a feed, an export or a published page can drive a screen.
This removes the recurring authoring workload that determines whether a signage estate stays current, and removes it as a dependency rather than reducing it.
Video assets are distributed to devices in advance and played from local storage, so estate-wide playback at 1080p and 30fps does not depend on network conditions at play time.
And it goes out live when it needs to. A trust briefing or a leadership address streams from the room it is happening in to every screen on the campus, alongside the scheduled material that is already cached on each device. Same license, same screens, nothing extra to buy.
Time-limited codes issued per room, displayed as digits and as a QR code, with every request accepted by the host before anything reaches the screen. Joins are restricted to declared networks and individually attributable. Applicable to consult rooms, teaching rooms and MDT meetings. Casting detail →
Priority interruption across every screen and every campus simultaneously, initiated and cleared from a mobile device. No scheduled content outranks it. Signage platforms are generally architected around scheduling rather than interruption, which is where this differs.
Continuous per-device condition reporting across the estate, included rather than provided by a separate device management platform.
Ticket state, room schedules and campaign inventory require no patient record, and the platform holds none. Out of scope by design: patient room boards displaying name, condition or care team, and any integration with a clinical record system.
Queue state, room bookings and campaign inventory need no patient record, and the platform holds none. Out of scope by design: anything naming a person or their condition.
None of the above is a playlist somebody maintains. Each screen is a surface for Ava, which holds one understanding of the place and knows which room it is in, so what belongs there at that hour is composed rather than authored. A clinic list and a department move are enough for her to keep a concourse right without anybody opening a template.