Hospital staff spend about 30 minutes a week each showing people the way to the cafeteria, the restrooms, the elevators or the exit, according to a 2025 survey of 301 US hospital employees published in the HERD journal. Nearly 44% of them had faced incivility from visitors who got lost. Run the arithmetic for a hospital with 3,000 employees and half an hour a week becomes roughly 78,000 hours a year, the equivalent of about 37 full-time positions spent giving directions. That is the budget line digital signage for healthcare competes for, long before anyone mentions patient experience scores.
For an integrator, the buyer is rarely a single building. AHA’s Fast Facts for 2026 count 3,567 of the 5,121 US community hospitals as part of a health system, so a signage project that starts in one lobby tends to get specified for every site the system owns. This guide covers the three jobs hospital screens do, the data feeds behind them, the privacy and alert rules hospital IT will hold you to, and what it costs to run digital signage software built for screen networks at health-system scale. A hospital network buys screens, but it signs off on the data, the privacy rules and the alert override behind them.
Digital signage for healthcare: three jobs on one network
Digital signage for healthcare is a network of screens across hospitals and clinics, run from one content management system, that shows wayfinding, queue status, health information and staff messages. Compared with a retail network, it draws on live hospital data and works under patient privacy rules, and both shape how the software has to be built. Three jobs account for most of the screens you will install, each with its own audience, data source and failure mode.
Hospital wayfinding across a multi-building campus
Hospital wayfinding looks like the mall problem and behaves differently. A shopper browsing a directory has time. A visitor looking for oncology on a Tuesday morning is anxious, often elderly, sometimes in a wheelchair, and already late. Campuses add skybridges, wings named after donors, entrances that close at 8 pm and an emergency department that becomes the only way in after dark, so the routing logic needs step-free routes, opening hours and the live status of every entrance.
The steps we laid out for a shopping-centre wayfinding rollout still apply: find out what people ask for, pick the hardware, design the map, keep it current. In a hospital the last step is the hard one. Clinics move between buildings, departments get renamed after a merger, and a directory that sends people to last year's location does more harm than no directory at all. Pull room and department data from the facilities team's space management system, where it already lives, and a change made once reaches every kiosk.
Kiosks have one obvious limit: nobody can carry them. A QR code on the directory that hands the route over to the visitor's phone covers the rest of the walk, past the elevator bank and down the corridor where the screens run out.
Patient queue screens in waiting areas
A patient queue management system issues a ticket at check-in, at the desk or a kiosk, and calls the patient to a room or counter when their turn comes. The waiting-room screen is its visible end: ticket number, destination, a chime and, in better setups, an estimated wait. Voice announcements earn their place here, because a share of the people waiting cannot read a screen across the room.
Integration is where integrators lose time. Queue vendors expose their data in different ways, some through a documented REST API or webhooks, others through a database view or a display client of their own that they would prefer you keep. Decide early between rendering the queue in your own player and embedding the vendor's screen. The choice also assigns the 7 am phone call when the display freezes, to your support desk or to the vendor's.
Wait estimates pay off beyond patient comfort. A patient told by the screen, or by a text message, that they have 25 minutes can go for a coffee and leave the front desk in peace. One more reason the route to the cafeteria belongs on the wayfinding screens.
Staff screens in back-of-house areas
The third job of digital signage in hospitals gets the least attention in vendor brochures and often the most use. Screens in staff corridors, break rooms and huddle areas carry unit census and bed status, safety notices, shift messages and the policy updates nobody reads in email. Turnover makes them more useful. NSI's 2026 retention report puts hospital staff turnover at 18.5% for 2025, which means a hospital replaces close to a fifth of its workforce every year, and each new hire has to learn how the unit runs.
Staff screens also change the display rules. A bed board in a nurses' station can show far more than a lobby screen, because it is a working tool for clinicians. Nurses' stations are visible from the corridor, though, so screen placement and viewing angle become part of the privacy design and belong in the site survey.
| Wayfinding | Patient queue screens | Staff screens | |
|---|---|---|---|
| Audience | Patients and visitors, many on a first visit | Patients waiting in one area | Clinical and support staff |
| Main data source | Space management system, opening hours, entrance status | Queue management system, check-in kiosks, appointment schedule | ADT feed, staffing tools, internal communications |
| Allowed on screen | Departments, routes, accessible entrances | Ticket numbers, destination room, expected wait | Census, bed status, safety and shift messages |
| Cost of a failure | Lost visitors and interrupted staff | Missed calls, a crowded desk, privacy complaints | Stale bed status, missed safety notices |
The data behind hospital digital signage
In digital signage for healthcare, a screen is only as current as the feed behind it, and the feeds belong to hospital IT. Expect to work through their integration team, their interface engine and a change process measured in weeks. The good news is that signage asks for little.
HL7 v2 feeds from the hospital's integration engine
Most hospital systems still talk in HL7 v2, the event-message format behind admissions, transfers and scheduling. ASTP's survey of health information exchange organizations found 90% routinely receiving HL7 v2 admission, discharge and transfer (ADT) messages, against about one in five working with FHIR APIs. Inside a hospital, those messages pass through an integration engine such as Rhapsody, Infor Cloverleaf or Mirth Connect, and your signage platform becomes one more destination the interface team configures.
Signage only reads. Write access, the slow and expensive part of connecting software to an EHR, never comes up, which makes a screen feed an easy request for the interface team. Ask for a filtered feed carrying only the message types and fields the screens need. The less patient data reaches your platform, the shorter every later conversation about privacy.
| HL7 v2 message | Trigger event | What a screen does with it |
|---|---|---|
| ADT^A01 | Patient admitted | Adds the patient to unit census and the bed board |
| ADT^A02 | Patient transferred | Moves the patient between unit boards |
| ADT^A03 | Patient discharged | Frees the bed on capacity screens |
| ADT^A04 | Outpatient registered | Adds a ticket to the waiting-room queue |
| SIU^S12 | Appointment booked | Adds the visit to a clinic's day board |
| SIU^S13 / S14 | Appointment rescheduled or modified | Moves the slot and recalculates waits |
| SIU^S15 / S26 | Appointment cancelled, or patient did not show | Removes the slot so the queue moves up |
Queue systems, FHIR and vendor APIs
Plenty of sources skip HL7 altogether. Patient queue management system vendors usually offer a REST API or webhooks, newer EHR developer programs expose FHIR resources such as Appointment and Location for read access, and the cafeteria menu may come from a catering system with a CSV export. Wire each of these straight into the player and every screen turns into its own integration project.
The architecture that holds up puts a thin integration service between the hospital's sources and your CMS. It receives the feeds, strips anything the screens should not show, merges the rest into display-ready data and hands that to the players, which only render. We build players this way on purpose: a commercial display has limited processing power, and a player that merges five feeds on its own starts to lag. For a single queue screen, the sequence looks like this:
- Agree the source and message types with hospital IT in writing, and name an owner for the feed when it breaks.
- Get a test feed with synthetic patients before any production data arrives.
- Map the fields and drop every one the screen does not need, at the integration layer, before anything reaches a player.
- Define fallback content for a feed that stops for two minutes and for one that stays down for two hours.
- Run the screen alongside the existing process for a week before staff rely on it.
Privacy and safety rules for healthcare digital signage
A hospital screen publishes hospital information in a space anyone can walk into. Three sets of rules follow from that: patient privacy, emergency messaging and the security review hospital IT runs before any device joins its network.
Patient names on public screens under HIPAA and GDPR
US rules allow more than many integrators expect. HHS states in its FAQ on sign-in sheets and waiting rooms that providers may call out patient names in waiting rooms, because the Privacy Rule permits the incidental disclosures that follow, and a queue screen works by the same logic. The condition is reasonable safeguards and the minimum necessary standard: a name may appear, the medical reason for the visit may not. A queue screen headed "Oncology" with full names under it discloses a diagnosis, even though no single field on it is clinical data.
Europe pushes harder. Under GDPR's data minimisation principle, a ticket number that calls the patient just as well beats a name, and the hospital's data protection officer will make the same argument. Design European deployments around numbers from day one.
Under both regimes, the deciding choice is architectural. If names and other identifiers never reach the signage platform, the platform stays out of the flow of protected health information. Once it receives them, the vendor handling that data on the hospital's behalf becomes a business associate, with the BAA chain and safeguards that come with the role. In practice, a deployment usually ends up with three zones:
- Public waiting areas – ticket numbers, destination room or desk, expected wait. Names only where the hospital has decided to accept them, and never next to a specialty that implies a condition.
- Corridors and lobbies – no patient data.
- Staff-only areas – census and bed status as the clinical team requires, with every screen position checked from the visitor's side of the counter.
Emergency alerts that override the schedule
When a hospital calls a fire, an evacuation, a lockdown or a severe weather warning, every screen in the affected zone should drop its loop and show the alert. Hospitals already run mass notification platforms for this, and the signage platform subscribes to them. Singlewire's InformaCast, for example, reaches signage systems through CAP (the Common Alerting Protocol), its API connector, RSS, HTTP or JavaScript.
An alert depends on four details:
- Alert content runs on a priority layer above every schedule and playlist, with audio wherever the screen has speakers.
- Targeting goes down to site, building and floor, so a lockdown in one hospital leaves screens at the system's other sites alone.
- Delivery must not depend on a healthy CMS. A server down for maintenance still has to pass the alert through.
- An explicit all-clear ends the override and is logged with timestamps for the incident review.
If we had to pick one feature to get right first, it would be this one. The hospital will test it at its next drill, with the safety officer watching. Signage stays a second channel next to overhead paging and staff devices, and nobody expects it to replace them, but a screen still showing the cafeteria menu during a lockdown is the failure everyone remembers.
The security review by hospital IT
Hospital IT reviews every networked device, and a fleet of players running a third-party app gets a closer look than most, since medical devices share the same infrastructure. Expect to be asked for specifics:
- Network placement – players on their own VLAN, apart from clinical systems and medical devices, opening outbound connections only.
- Device identity – one revocable credential per player.
- Encryption and updates – TLS on every connection and signed app updates, so a player cannot be tricked into installing someone else's code. Hospital IT will also want the procedure for cutting off a compromised player.
- Hosting – the location of the CMS and its logs, which matters for HIPAA contracts and GDPR transfers alike.
- Testing – the date of the last penetration test and the issues it fixed.
The list overlaps with the six questions we suggest putting to any signage provider, and the answers come easier when you own the platform's code. For reference, the systems we have run for IMS Sensory Media over six years have not had a single breach.
Scaling digital signage for healthcare across a hospital network
One hospital is a project. Twenty hospitals are a platform, with an operations team, a permission model and a licensing bill to match, and the decisions made for the first site either carry over or get rebuilt at site four.
One CMS for many sites, roles and inherited fleets
Health systems grow by acquisition, and each acquired hospital arrives with its own screens. One site runs LG webOS displays, another Samsung Tizen, the outpatient clinics use Android boxes and the old education center has Windows PCs behind its TVs. A platform for a health system has to run all of them from one CMS, which is why we build player apps natively for five operating systems instead of asking the client to standardise hardware first.
Roles matter as much as hardware. The system's communications team publishes flu-season campaigns to every site, facilities at each hospital own their wayfinding data, a clinic manager edits the queue screen text in one department, and none of them should be able to break anyone else's screens. Locked templates keep the brand consistent while local editors change the content. Built as multi-tenant from the start, the same structure lets an integrator serve several health systems from one platform, each with its own branded dashboard.
Offline playback and monitoring on hospital networks
Digital signage in hospitals runs on busy, uneven networks. Guest Wi-Fi is congested, basements and stairwells have weak coverage, and IT schedules maintenance windows without asking marketing. Players in the systems we build cache around two weeks of schedule and content, and they switch to new content only after it has fully downloaded, so a dropped connection leaves the loop playing.
Queue screens are the exception, and the reason a hospital network needs fallback rules per screen type. A queue screen showing stale numbers does more damage than a blank one, because patients act on what it says. When its feed stops, the screen should switch to a message such as "Please wait to be called at reception" instead of freezing on the last ticket.
Monitoring closes the loop. The platform should flag offline players, failed downloads and outdated schedules per site and raise alerts on its own, so the integrator's support desk hears about a dead screen before a ward nurse does.
Licensing cost at health-system scale
Per-screen subscriptions look small on one screen and large on a network, which is the scale digital signage for healthcare is usually bought at. If you resell a SaaS platform under your own brand, white-label plans list at roughly $8 to $45 per screen per month, the range we found when comparing vendors' offers. A health system with 20 hospitals and 50 screens in each already runs 1,000 of them.
| Screens | Per year at $8 per screen per month | Per year at $45 per screen per month | Three years at $8 |
|---|---|---|---|
| 300 | $28,800 | $162,000 | $86,400 |
| 1,000 | $96,000 | $540,000 | $288,000 |
| 3,000 | $288,000 | $1,620,000 | $864,000 |
An owned platform turns that bill into a one-off build, from about $15,000 for a basic CMS with one player app. Each integration (the HL7 feed, the queue system's API, the alert subscription) is scoped as its own piece of work, and hosting grows with the fleet without a fee attached to every screen. Maintenance stays on the budget either way, because display makers update their operating systems whether or not you own the code. In the cost example from our white-label guide, a basic owned build for 500 screens paid for itself within its first year.
Choosing hospital digital signage software
Neither route wins everywhere. Network size, the number of live feeds and ownership of the client relationship decide it.
Signals that an off-the-shelf platform is enough
A single clinic or a small practice group with a few dozen screens, content that is mostly health education loops and menus, and no live feeds: healthcare templates in SaaS signage products are built for exactly this. The subscription stays modest at that size and setup takes days. If your client looks like this, sell them a SaaS plan and put your effort into content.
Signals that an owned platform pays off
The balance shifts when several of these apply at once:
- The client is a health system, or you serve several, and screens run into the hundreds.
- Screens depend on HL7, queue or alert integrations that a SaaS vendor supports only through its partner list, if at all.
- The hospital wants patient data handling it can audit end to end, hosted in a region it chooses.
- You want to resell under your own brand and set your own prices.
- After a few acquisitions, the fleet mixes hardware from three or four vendors.
With three or more of these on the list, both the per-screen bill and the integration limits point toward hospital digital signage software you own.
A first project smaller than the whole network
Few health systems commission a platform before they have seen something work. A wayfinding kiosk in one lobby, or a single queue screen wired to a real feed, proves the integration path, the privacy design and the support model at small scale. It also gives the hospital's IT team one deployment to review instead of fifty, and lets you test a development partner before handing over anything close to your core platform.
That is how we usually start with integrators. Fingoweb builds the software (players, CMS and integrations) and stays technically responsible for it after launch, while hardware, installation and on-site service remain with you. This article draws on two parts of our work: signage platforms running on more than 15,000 active players in retail and DOOH networks, and healthcare software built to HIPAA and GDPR requirements, including patient apps integrated with medical devices. If a health system has asked you for wayfinding, queue screens or staff boards across its sites, we can scope a digital signage platform you own around its feeds and its rules.
FAQ – digital signage for healthcare
Quick answers to the questions about digital signage for healthcare that come up most often when a hospital first asks for screens, the regulatory ones included.
What is digital signage in healthcare?
Digital signage in healthcare covers the networked screens in a hospital or clinic whose content is managed centrally: lobby directories, wayfinding kiosks, queue displays, cafeteria menu boards, patient education screens and staff boards. Much of that content comes from hospital systems such as scheduling, admissions and mass notification, so the screens change through the day with the hospital's own activity.
What are the requirements for healthcare signage?
In the US, signage in a hospital answers to several rule sets at once:
- ADA Standards – permanent room signs need tactile characters and braille under section 216, so a screen cannot replace the sign on a restroom door. Building directories and signs posted for seven days or less are exempt from that section.
- Life Safety Code – exit signage follows NFPA 101, which hospitals in the Medicare program must meet.
- HIPAA – any screen showing patient information falls under the minimum necessary standard.
- Readability of the content itself: contrast, text size and audio for queue calls.
Digital screens sit on top of the static, code-required signs and do not replace them.
Can a hospital queue screen show patient names?
In the US it can, within limits: HHS accepts names called out in a waiting room or visible on a sign-in sheet as incidental disclosures, and a queue screen follows the same logic, provided nothing reveals the reason for the visit. Build in an opt-out for patients with safety concerns, and leave names off entirely in behavioral or sexual health clinics, where the location alone says too much. In the EU, ticket numbers are the safer default under GDPR.
How much does digital signage cost for a hospital?
The cost of digital signage for healthcare splits into four parts:
- Hardware – commercial displays, players and kiosks, usually supplied and installed by the integrator.
- Software – a subscription at roughly $8–45 per screen per month at list prices, or a one-off build from about $15,000 for an owned platform.
- Integrations – priced per feed.
- Content and support – someone has to produce patient education content and answer the call when a screen goes dark.
For a single clinic a subscription is usually cheaper, while across a health system an owned platform tends to pay for itself within a few years.
What is wayfinding in a hospital?
Hospital wayfinding is the set of signs, maps, screens and apps that gets patients and visitors from the parking lot to the right room without stopping staff to ask. It starts before arrival: appointment letters and the hospital website should name the entrance and the parking structure, since the main lobby is among the places where staff in the HERD survey were asked for help most often. On site it combines static signs, digital directories, kiosks and directions on the visitor's phone.
What are the benefits of digital signage in healthcare?
For hospitals, the measurable ones are fewer interruptions for staff, shorter perceived waits when patients can see their place in the queue, and updates that reach every site in minutes, with no reprint cycle. During an emergency, one alert channel reaches every screen at once. For integrators, the benefit is recurring work: content operations, integrations and support contracts tied to a network that grows with the health system.
