Plan a patient room sign around the pillow-to-screen distance: 30 ft of viewing per inch of capital height, 20 ft per inch for fast reading. Run one locked browser per room on its own URL from one hospital server, blank the page between patients, and treat everything shown as protected health information.
A sign in every patient room is two problems in one enclosure. The screen has to be readable from a pillow, at 6 to 10 ft, by someone lying down and not feeling well. The content is per-room protected health information that has to arrive, refresh and disappear on demand. Both have short answers. Size the letters first: 30 ft of viewing distance per inch of capital letter height, 20 ft per inch when the patient should take it in at a glance. Run one locked browser per room, each on its own address, off one hospital server. Blank the page when the room is empty, encrypt everything, and mount the screen where the corridor cannot read it. The rest of this page works the numbers and the build, option by option.
Letter height sets the screen size
Start from the pillow, never from a screen size. The legibility planning figure used for public signs is 30 ft of viewing distance per inch of capital letter height, with the FHWA as its basis, and 20 ft per inch is the safer figure when the reader should catch it at a glance, which is the right target for a bedside sign. At 8 ft that is 0.27 in of capital height minimum, 0.40 in for comfortable reading.
Pixels follow from the panel. A 16:9 panel's height is about 0.49 of its diagonal, so a 21.5-inch, 1920 x 1080 panel stands about 10.5 in tall, its 1080 pixel rows sit 0.0098 in apart, and 0.40 in of capitals is 41 pixels. At bedside distances the resolution is never the constraint: a panel this small already carries more pixels than the eye needs from 8 ft, so pick the panel by mounting space and line count, then set fonts by the pixel numbers. Build the page at the panel's native resolution, because a mismatch scales your sizes and strands content in a corner; the fix for content that lands in one corner shows what that looks like. The full sizing method, including standing readers and angles, is in what size digital signage screen do you need.
Example: a nine-foot room, one 21.5-inch sign
Scenario: a 9 ft wall-to-wall room, the sign on the wall opposite the bed, a lying patient's eyes 9 ft away.
- Headline capitals: 9 ft ÷ 20 ft per inch = 0.45 in.
- Body capitals: 9 ft ÷ 30 ft per inch = 0.30 in.
- On the 21.5-inch panel at 0.0098 in per pixel: 0.45 in is 46 px of capital height, 0.30 in is 31 px.
- Line budget: body line pitch is 1.7 x 0.30 = 0.51 in, and the panel is 10.5 in tall, so 10.5 ÷ 0.51 = about 20 lines of body text fit.
- Verify on the wall: print a capital A at 0.45 in, tape it where the headline will sit, and read it from the pillow. If it fails, the distance or the font size was wrong, not the rule.
A 21.5-inch panel is generous at this distance. The same numbers shrink gracefully: at 5 ft, a visitor's chair distance, the comfortable figure is 0.25 in, about 26 px on the same panel.
Three ways to build a room sign
Three builds cover every patient room. The first two carry live, per-room content; the third carries content that rarely changes.
| Build | What it is | Pick it when | What to watch |
|---|---|---|---|
| Consumer TV plus a small player | an ordinary television with a compact player feeding its HDMI input | rooms that already have a bracket and a tight per-room budget | consumer power-saving and sleep behavior fight a sign that must appear the moment a room fills; the consumer TV or commercial display question for a waiting room sign is the same tradeoff, room by room |
| Commercial display plus a small PC or player box | a display built for sign duty and a box running the locked browser | IT wants one managed system image across the whole ward | two devices per room to power, mount and patch |
| Card-fed all-in-one signage unit | panel and player in one, playing picture and video files from a memory card or USB stick with no subscription and no account | the static loop: welcome, visiting hours, Wi-Fi code, chaplain times | it plays files, so a live per-room page or a tailored discharge video is outside what it does; it is designed to restart its loop after a power cut |
One address per room, one locked browser
The per-floor server plan is right, with one change: make it one server for the hospital, not one per floor, and give every room one address, a path per room number such as /room/412. A 30-room floor polling every 5 seconds makes 6 requests a second, which is nothing for one small server. Each floor box adds a machine to patch, back up and monitor, and buys nothing at that load.
Run each room's browser in kiosk mode. Microsoft Edge documents a full-screen digital-sign option in its kiosk mode that runs one address full screen; the other major browser drives the same kind of mode from a start-up switch. Configure the room address in the kiosk setup and the page returns on its own after a power cut, because kiosk mode starts where you told it to start. One player per screen is the right economics here; one signage player or one per screen for four TVs works through when a shared player makes sense, and a patient room is not that case, since every room needs its own address.
The staff trigger rides the same rail. A staff button posts an event to the server, the room page polls every 5 seconds, and the discharge video is playing within one poll interval, so 5 seconds at most from button to picture. Keep the push endpoint for staff only.
Blanking, sleep and the room's light
Blank in software; it is the dependable design. The page is already loaded, so when the server marks the room empty it goes black, and it returns within one 5-second poll when the room fills. Wake-on-signal is the fragile road: it needs the player and the panel to both honor HDMI-CEC, and commodity panels honor it unevenly, so take any wake feature as a bonus and build on blanking. If the player is a Windows PC that CEC traffic keeps waking, the documented stop is in Device Manager: open the display adapter's properties, Power Management tab, and clear 'Allow this device to wake the computer'.
Blanking stops the information, not the backlight. A monitor in this size class still draws roughly 20 to 40 W lit and black, so real savings need the panel off. Where the hospital schedule allows it, let the server command a night window too, say 21:00 to 06:00 for unoccupied rooms, so the panel powers down for real. Dim for evenings as well; setting digital signage brightness for the ambient room light gives the brightness numbers for the light in the room at each time of day.
Treat every pixel as PHI
Whatever a room address serves is protected health information, the information HIPAA governs, and so are the server, the hospital network, every screen and the eventual disposal of every unit. Three rules hold the line:
- TLS on the room addresses, even inside the building. It costs one internal certificate and takes the plaintext question off the table.
- Minimum necessary on screen: name, care team, the day's plan. Results and diagnoses stay in the record system; the sign is a bedside courtesy, not a chart.
- Mount so the corridor cannot read it. An LCD reads well off its straight-on axis, so stand in the doorway and check what a passerby sees before you drill. The viewing-angle test before you drill explains the off-axis behavior and the test.
One electrical rule belongs to the room itself. The patient vicinity, commonly taken as the 1.5 m around the bed, carries its own equipment requirements in hospitals. Put the sign on the foot wall or the far wall, and clear anything mains-powered near the headwall with biomedical engineering before you mount it.
When the card-fed unit or a waiting-room sign is the right call
Skip the whole server build when the content is static per room type. Welcome loops, visiting hours and the guest Wi-Fi code are identical in every room of a unit, and a card-fed signage unit plays them with no internet, no account and no subscription; that is the job our waiting room screens are built for. If the loop is worth building properly, IMD Signage Studio, our free Windows app, makes the slides and writes the show to a memory card or USB stick. The card covers the general loop and leaves the tailored discharge video to the server build.
A waiting-room or lobby sign is a different job again: one screen, mixed audience, general content, standing readers. If the first phase is really about family waiting areas, start with clinic waiting room signage: one screen or two jobs and size that screen for standing readers at its own distances. And if patients are meant to touch the screen for menus or education, order that as its own touchscreen project with its own lockdown and review.
Recommendation: For live per-room content, order a commercial display and a small player per room, 21.5-inch panels for pillow-to-screen distances up to 10 ft, capitals set to the pixel sizes from the example, and the browser locked to the room's own address. Run one TLS server for the whole hospital with a 5-second poll, blank each page when the room empties, and add a night power window where the schedule allows. Use a card-fed unit only for the static loop that is identical in every room. Put the biomedical-engineering check and the PHI review ahead of the first install, because both move the mounting and the content.
What to send with the quote
Settle these in writing before the first screen mounts:
- Pillow-to-screen distance per room type, with capital heights from the example in inches and pixels.
- Mount location per room type, foot wall or far wall, and orientation, landscape in nearly every room.
- Panel size per room from the letter-height numbers; a 21.5-inch panel covers 9 ft with about 20 lines of body.
- A network point and an outlet at each screen, on the circuit the hospital approves.
- Who fires the discharge video, from what device, and what the server logs.
- The content list, with a PHI review of every field that reaches a room address.
- For any card-fed unit in the mix, its software, ports, power, orientation, lead time and warranty confirmed in the quote. Our display range is quoted per project.
Questions
How many room signs can one small server carry?
Count poll traffic. A room polling every 5 seconds makes 0.2 requests a second, so 200 rooms make 40 requests a second. At a few kilobytes per response that is well under 1 MB per second, which one current small office server handles without tuning. A server per floor buys nothing at that load and costs one machine to patch, back up and monitor on every floor.
Can the room signs ride the guest Wi-Fi network?
No. Each room address serves protected health information, so the screens belong on the hospital's managed network, on their own segment with access to the signage server and nothing else. Where a wired jack is missing, put the screen on the hospital's managed wireless, never the guest network, and have IT confirm the segment rules before the first screen mounts.
Should patients be able to touch the screen?
Leave input out of the first build. Kiosk mode already keeps the browser on its page, and the nurse-call system stays the path for requests. If a unit later wants patient interaction such as education or meal ordering, order it as its own touchscreen project with its own lockdown, mounting height and PHI review, since touch changes the hardware and the mounting.
Planning information, not legal or engineering advice. Rules differ by place: check codes and permits with your local authority and your licensed trades.