Healthcare

A waiting room that
answers itself.

Most of what a waiting room asks is the same five questions. Put the answers on the wall — where to go, how long, what to bring, what changes today — and the desk gets the time back.

Plans, prices and trials are set by your ScreenQube partner.

A waiting-room screen showing the token now being seen, the room number, and the next four tokens.

Where it ends up

You work in a browser.
They see the wall.

The screen above is what you publish. This is where it ends up — a display a customer stands in front of, driven by a player that fetched it on its own.

A now-calling screen listing patients and their room numbers in a clinic waiting area, with people seated below.
A now-calling screen in a clinic waiting area. You work in a browser. This is the other end of it — a display a customer stands in front of, driven by a player that fetched its content on its own.

What goes on the screens

Six things worth putting up.

Every one of these is ordinary media, arranged in Composition and sent out by Publish. Nothing here needs a separate system.

Department wayfinding

Which floor, which wing, which lift. The single most-asked question at any hospital desk.

Clinic times and delays

Which clinics are running, and which are behind.

Health information

Seasonal advice, screening reminders and pre-appointment instructions, on a schedule.

Infection control and policy

The notices that have to be visible in every waiting area.

Staff and ward notices

Back-of-house screens on the same platform as the public ones.

Consent, charges and rights

The printed A4 sheet, legible and current, and changed in one place.

Where the screens go

Four walls that earn it.

  1. Out-patient waiting

    The longest dwell time in the building, and the screen people actually read.

  2. Reception and main entrance

    Wayfinding first, everything else second.

  3. Ward corridors and day units

    Visiting hours, ward notices, and what changed today.

  4. Staff rooms and handover areas

    Rotas, safety notices and training dates.

How it is run

Four steps, then it runs itself.

The same four steps whether you have four screens or four hundred. This is the real console, not an illustration.

  1. Add facilities, pair screens

    One facility per site, branch or building. A screen joins by showing a registration code, which you type in once. Switch between facilities from the header.

  2. Upload and compose

    Media goes into the library, in folders, with tags. Composition arranges it into zones — your own files, plus App Store apps like weather, news or a ticker.

  3. Publish three ways

    On a schedule, with day sequences. Or QuickPlay, which the console describes as displaying content instantly for a flash sale or an emergency. Or as the default composition a screen falls back to.

  4. Check it, without going there

    Live Monitoring reports each screen's state. Take Screenshot shows what one is really displaying. Reload, clear the cache or reboot it remotely.

What it fixes

The three complaints we actually hear.

The desk answers the same directions question four hundred times a week.
A wayfinding board answers it without anyone speaking.
Printed notices in a clinical area go out of date and nobody notices.
One library, one publish, and Audits showing who changed what and when.
A screen in a side corridor has been off for a fortnight.
Live Monitoring counts disconnected screens as a headline tile, not as a line in a report.

Set it up as

The solutions this usually becomes.

Nearby

Other industries with the same problem.

Questions

What healthcare teams ask first.

Can it call patients from our patient administration system?

No integration with a patient administration or queue system has been observed in the console. Screens are published from the Media Library and Composition.

Can different sites run different content?

Yes. Each site is a facility with its own screens, and Publish targets the facilities you choose.

Who can change what is on a ward screen?

Users belong to groups, and Audits records every create, update and delete against the person who made it.

Does it need a PC behind every screen?

No. An Android player app runs on the display itself and fetches its content.

Put it on every screen.

Talk to us about becoming the partner who sells it.

We will introduce you to the partner who covers your region.