# QR codes for hospitals

> Hospital QR codes work at institutional scale only with a register: every code's URL, location, owner and review date recorded, one template, one domain. The highest-value chain runs from the car park to the ward — wayfinding codes at each decision point, never carrying patient data.

Source: https://useqr.app/qr-codes-for/hospitals · Last reviewed 2026-08-21 · UseQR is free forever, MIT licensed, no signup.

---

## Run codes like estates runs signs

The clinical rules — no patient data in payloads, printed alternatives always, wristband
constraints — are on the [healthcare](/qr-codes-for/healthcare) page. What a hospital adds
is scale: hundreds of codes across dozens of departments, printed by different teams over
years. Without governance, that decays into dead links on permanent signage.

The fix is a **code register**, exactly like an estates asset list: for every code, its
URL, physical location, owning department, print date and next review date. Add every new
code at print time; walk the register annually with a phone. A hospital that cannot say
how many QR codes it has displayed has some pointing at retired pages — link rot on a
laminated sign outlives the intranet page it pointed to.

One template, one official domain, and [bulk generation](/bulk) from the register keeps
the estate consistent.

## The parking-to-ward problem

The hardest journey in the building starts in the car park: anxious visitor, unfamiliar
site, appointment letter naming a ward. Chain the codes along the actual decision points:

| Point | Code links to |
|---|---|
| Appointment letter | Directions page for that clinic, plus a [geo pin](/location-qr-code) for the right car park |
| Car-park exit | Site map with walking routes |
| Main entrance and each junction | Step-free route to each department |
| Lift lobbies | Floor directory |

Corridor sizing and mounting heights follow the
[healthcare signage numbers](/qr-codes-for/healthcare); pair every code with printed
directions, since many visitors will not scan.

## Visitor information

Ward-specific visiting hours, what to bring, infection-control rules — printed on the ward
door with a code to the live version. The printed sheet answers today's visitor; the code
stays correct when policy changes tomorrow.

## Discharge and the token pattern

Discharge codes may link generic aftercare pages freely. Anything patient-specific must
use an **opaque token** resolved by an authenticated portal — the
[token-not-record pattern](/docs/security/qr-codes-in-hipaa-contexts) — so a photographed
letter leaks nothing. Never encode the record; encode a pointer only the system can
resolve.

## FAQ

### How should a hospital manage hundreds of QR codes?

With a register: URL, location, owner, print date and review date for every code, managed
like any estates asset list. Review annually with a phone in hand. Unregistered codes on
permanent signage are how hospitals end up with laminated dead links.

### What should hospital wayfinding QR codes link to?

The step-free route to a specific destination from the code's own location — not a
generic site map. The appointment letter's code should carry the clinic's directions page
and the correct car park, since the journey starts before the building.

### Can discharge instructions go behind a QR code?

Generic aftercare pages, yes. Patient-specific instructions need an opaque token that an
authenticated portal resolves, so the code on a photographable letter identifies nothing.
A printed copy must always accompany the code.

## Try it

- https://useqr.app/url
- https://useqr.app/location
- https://useqr.app/feedback