signage · content · patient wayfinding

Charles Trinh — Digital Signage, Las Vegas NV

Charles Trinh — Digital Signage, Las Vegas NV
Charles Trinh — Digital Signage

Digital signage in healthcare: wayfinding that reduces staff interruptions, content governance that survives an incident, and players that keep running when the network does not.

Wayfinding is the business case

Signage earns its place by reducing the number of times a patient asks a person where to go, not by showing a lobby video.

Measure the interruptions at reception before and after, because that number is the argument that survives budget review.

Design for the person arriving anxious and late, which means larger type, fewer destinations per screen, and no rotating content that hides the answer.

Content governance

Who may publish, what may be published, and how fast something must come down when it is wrong.

A single wrong price or a stale clinic closure on a screen is a clinical communication error, not a marketing mistake.

Keep an emergency takeover path tested monthly, because during an incident the screen is one of the few channels you control.

Player resilience

Players must boot into content without the network: local cache, scheduled playlist and no dependency on a live API to render.

Avoid consumer sticks in clinical areas; they need updates, credentials and physical access nobody wants to manage across fifty screens.

Include watchdog reboot and a documented recovery procedure, because a black screen at a lift lobby is discovered by patients first.

Network and security posture

Put signage on its own VLAN with no route to clinical systems and a content feed pulled rather than pushed.

Sign the content packages where the platform supports it, since the screen is an unmonitored endpoint with a public display.

Patch and inventory players like any other device, because a fleet of unpatched Android boxes is an unmanaged estate.

Accessibility and language

Contrast, font size, reading time and multi-language rotation are requirements in a public building, not enhancements.

Test with a person who does not know the building; that is the only usability test that predicts the outcome.

Provide the same information in a static form nearby, because not every patient can read a screen.

Lifecycle and disposal

Plan screen replacement on a cycle and keep the mounting and cabling standard so a swap is an hour, not a day.

Wipe and dispose of players with the same rigour as any other device that held credentials.

Record what was installed where; signage inventories are almost always stale.

How I do it

One trace of a real case with timestamps at every hop, before any document is written.

A findings list naming the defect, the system, the owner and the date, reviewed monthly.

No attestation I did not test, and no template sold as an assessment.

Who owns the screen

Every screen needs a named owner who is accountable for what appears on it and for how quickly it can be changed, and that person is rarely in marketing. In a hospital the screen at a lift lobby is a clinical communication channel, and the owner should be the operational lead for that area rather than the communications team, because the operational lead is the one who will be asked why the closure notice is three days old. Marketing may write content; it should not be the only route to publishing it.

Publish through a small number of templates with defined slots, so the person updating a clinic closure fills a field rather than designing a slide. Templates also make the accessibility requirements structural, because contrast and minimum type size are properties of the template rather than good intentions. Where a team insists on bespoke content, the request is usually about a message that has no template, which is a signal that the template set is incomplete rather than that the content is special.

The screen as an incident channel

During a system outage or a building emergency, screens are one of the few channels that reach people who are not looking at their phones. Designing for that use means a takeover mechanism that can override every screen from one place, a rehearsed procedure for invoking it, and content that is legible at a glance without audio. Most estates discover during the incident that the takeover requires logging into each player, which is a design failure discovered at the worst moment.

Test the takeover monthly with a short, obviously-labelled exercise, and record how long it took to reach every screen. A monthly cadence sounds excessive until the first real event, when the difference between two minutes and twenty is the difference between a managed response and a queue at reception. The same mechanism serves the reverse case, clearing a stale warning from every screen quickly, which is the situation that actually happens more often.

Measuring whether it works

The two numbers that justify signage are the reduction in wayfinding questions at reception and the reduction in staff time spent redirecting people, and both are observable with a two-week count before and after. Without those numbers the signage budget competes with everything else on aesthetics, and aesthetics lose to clinical equipment every time. Take the measurement while the old signage is still in place, because the baseline is the harder half to obtain later.

Measure accessibility too, by asking three people who do not know the building to find a department using only the screens, and recording where they hesitate. Hesitation is the signal: a person who stops and looks around has been failed by the display, and the fix is usually fewer destinations on the screen rather than more arrows. This test costs twenty minutes and changes the design more than any review meeting, because it produces the specific place where the current layout stops working.

Signage and accessibility obligations

Public-facing information in a healthcare building carries accessibility expectations that are legal as well as ethical, and a screen that shows small text in a rotating carousel fails the majority of the people who need it most. Set a minimum type size by viewing distance, a minimum contrast ratio, and a maximum number of items per screen, and record those standards in the template rather than in a design guideline nobody opens. Test the result by standing at the actual viewing distance rather than at a desk, because the difference between a design review and a lobby is three metres and a queue.

Where the screen carries information that is also available elsewhere, keep the two consistent, because a patient who reads different information on the screen and the printed leaflet has been given a reason to distrust both. That consistency is a content ownership question rather than a technology question, and the answer is a single source for the information with the screen as one rendering of it. It costs an integration and it removes a recurring class of complaint, which is a trade most estates should make earlier than they do.

Screen inventory and the black screen

Maintain an inventory that maps each screen to its player, its location, its content channel and its owner, because the support call is always a description of a place rather than a device name. When a screen goes black the fastest path is knowing which player serves it and whether that player is reachable, and without the inventory the first ten minutes are spent walking to look at the back of the screen. Update the inventory when a screen moves, since a stale entry is worse than none when somebody is standing in a lobby under a blank display.

Proof

  • ONC (g)(10) self-test PASS, 317 of 317 subtests, April 2026 — public suite URL
  • 67 public hostnames, 51 serving, one AWS account
  • 104 clearinghouse enrolments across 53 jurisdictions
  • USCDI v7 proposal — Patient Digital Identity Credential — listed at isp.healthit.gov
  • SAM.gov UEI MVKQW9DKKGB8 · CAGE 20KM5 · NPI 1194645564
  • AWS Business Associate Addendum active since 18 August 2026

Where this work is delivered

Engagements run from Las Vegas and reach across the valley: clients in Las Vegas, NV; Las Vegas, Nevada; Henderson; Clark County, Nevada; and North Las Vegas, Nevada — plus remote delivery nationwide.

How an engagement runs

1. Trace one real case

Follow a single patient or claim end to end with a timestamp at every hop, before any document is written.

2. Written findings

A findings list naming the defect, the system, the owner and the date.

3. Monthly review

Review the list monthly and check whether the dates held.

Frequently asked

What is this service?

This page describes charles trinh — digital signage, las vegas nv — the scope, the failure modes it prevents and how the work is measured. It sits in the AV and IT Infrastructure category at trinh.io.

Where is the work delivered?

Engagements run from Las Vegas, Nevada across the valley — Las Vegas, Henderson, North Las Vegas, Spring Valley, Paradise, Winchester, Sunrise Manor, Enterprise, Summerlin, Clark County — and remotely anywhere in the United States. On-site work in the Las Vegas valley, remote delivery elsewhere.

What does it cost?

Standard rate $195 per hour, committed $165 per hour at twenty hours or more per week for three months or more; $1,600 standard day, $1,350 committed day. Scoped in writing before work starts, fixed fee where the deliverable is defined.

Who is Charles Trinh?

A technology architect in Las Vegas, Nevada, working in healthcare identity, consent and interoperability. Not a physician, not a medical practice, and not affiliated with any other Charles Trinh.

How does an engagement start?

With one trace of a real case and a written findings list naming the defect, the system, the owner and the date. The first call is twenty minutes and free: 702-559-3489.

Engagement

Scoped in writing before work starts; fixed fee where the deliverable is defined. First call is 20 minutes and free. 702-559-3489 · charles@trinh.io

Talk to Charles

Record

Profile

Healthcare technology architect working where federal regulation becomes production infrastructure. Built and operates a FHIR R4 clinical platform — SMART App Launch authorization server, patient and provider portals, SQLite — on a hardened single-host AWS estate of 67 public hostnames. The platform returned a self-test PASS on the ONC (g)(10) Standardized API test suite in April 2026, 317 of 317 subtests, publicly verifiable. Designed a consent architecture in which a permissioned ledger records patient grant, refusal and revocation as immutable events while all clinical data stays off-chain and encrypted per patient — no PHI on the ledger by design. Filed a proposed USCDI v7 data element with ONC on verifiable patient identity. Translates the Federal Register, HHS/CMS guidance and HITRUST requirements into architecture, controls and audit evidence.

Selected engineering scale

  • Self-managed estate of 67 public hostnames, 51 serving, on one AWS account.
  • FHIR R4 API with a SMART App Launch authorization server; patient and provider portals; an AI service layer; Hyperledger Fabric peer, orderer and CA; IPFS; a 337-table SQLite clinical store.
  • Two permissioned distributed ledgers in production, one operating a consent registry that records grant, refusal and revocation with no PHI on chain.
  • X12 005010 pipelines across eight transaction sets.
  • Designed, built, deployed and operated end to end by one person.

Credentials and standards work

  • Inferno (g)(10) self-test PASS, 317 of 317 subtests, April 2026 — the ONC Standardized API test suite. Standards validated: US Core 6.1.0, USCDI v3, SMART App Launch 2.0.0, Bulk Data 2.0.0. Public suite URL.
  • USCDI v7 public comment submission, April 2026 — proposed Patient Digital Identity Credential under the Provenance data class, listed publicly on the ONC Interoperability Standards Platform.
  • SAM.gov UEI MVKQW9DKKGB8 · CAGE 20KM5 · NPI 1194645564. AWS Business Associate Addendum active 18 August 2026.

Technical environment

AWS us-east-1 (compute, storage, messaging, SMS, email, voice) · Linux and systemd hardening · nginx · Fabric and EVM ledgers · FHIR R4 · X12 005010 · HL7 · SQLite · self-hosted mail, drive, search and monitoring · Git-based change control and CI release gates.

TRINH — Charles Trinh, technology architect
TRINH

Charles Trinh

Fractional CTO/CIO and Technology Architect — Healthcare Data, Identity & Regulated Infrastructure · Las Vegas, NV

Las Vegas, Nevada · US citizen · Fractional and project engagements

(702) 559-3489 Email Charles Trinh