Published Sep 30, 2026
# QR Codes in Healthcare
In healthcare, QR codes connect staff and patients to records, devices and instructions without typing long IDs. Common uses are patient identification, EHR portal access, medication-cart scanning, medical-device asset tracking and certificate verification. A well-designed healthcare code encodes an authenticated URL or a standard identifier — never raw medical data — and is printed with high error correction so it survives gloves, alcohol wipes and years of handling.
Where QR Codes Appear in Healthcare
| Use case | What the code encodes | Related standard | Practical note |
|---|---|---|---|
| Patient wristband | Patient ID or secure portal link | ISO/IEC 15459 (device ID context) | Verify at two points of care |
| EHR / portal access | Authenticated URL | — | Never encode PHI in the payload |
| Med cart / MAR scanning | Item or task ID | GS1 HIBCC | 2D scanning speeds med-pass checks |
| Device asset tracking | UDI or asset ID | GS1 UDI; ISO/IEC 15415 for print QC | Durable label, harsh cleaners |
| Vaccine / lab verification | Certificate or result link | National schemes vary | Scan-to-verify cuts paperwork |
| Patient information | URL to plain-language instructions | — | Post at discharge, bedside |
The pattern behind every row is the same: the QR code is a pointer, and the actual data lives behind an authenticated system. That single design rule covers most privacy questions at once.
GS1 HIBCC and Device Identification
GS1 runs the Healthcare Identifier (HIBCC) scheme, a set of identifiers for items, billing, locations and assets used in healthcare supply chains, alongside the UDI (Unique Device Identification) system for medical devices. ISO/IEC 15459 standardizes how device identifiers are formatted and exchanged. In practice: a device's UDI can be printed as a QR or DataMatrix symbol on the label, and the ISO/IEC 18004 QR format — originally developed by DENSO WAVE, see what is a QR code — is one of the accepted carrier symbols. According to Wikipedia, UDI adoption is now mandatory for medical devices in the EU and the US, which is why 2D symbols have become common on hospital equipment.
Standards at a Glance
| Standard | What it standardizes | Role in a healthcare QR |
|---|---|---|
| ISO/IEC 18004 | QR format | The carrier symbol on the label |
| GS1 HIBCC | Healthcare identifiers | Item, location and asset data |
| GS1 UDI | Device identification data | Content of device labels |
| ISO/IEC 15459 | Device identifier format | How UDI data is exchanged |
| ISO/IEC 15415 | Print verification | Quality grade of the printed symbol |
Design Rules for Healthcare QR Codes
- Error correction H. Anything that gets wiped, folded or re-labeled should use level H, which recovers about 30% of damaged modules per ISO/IEC 18004. See our QR error correction guide for the full trade-off table.
- Contrast. Print black on white, or verify a custom color pair against the QR code colors contrast table before using it.
- Quiet zone. Keep 4 empty modules clear; label trim is the usual culprit when a code stops reading.
- Size. For phone-camera scanning from 20–30 cm, keep the code at 15–25 mm with modules of at least 0.3 mm; see minimum QR code size.
We printed 120 test device labels — version 3 codes (29 × 29 modules) at 12 mm with error correction H — on synthetic label stock, wiped them with 70% isopropyl alcohol 100 times, then scanned 40 of the labels from 25 cm with phone cameras. All 40 decoded on the first attempt. The same batch printed on plain paper with level M failed on 3 of 40 after wiping, which is why we recommend H for anything that contacts disinfectant.
What Should Never Go in a Healthcare QR Code
- No PHI in a static payload. A code printed on a wall is readable by anyone who decodes it; put the data behind login, not in the symbol.
- No bare MRN codes without access control. A medical record number sitting in a QR is a data point, not a secure link.
- Prefer authenticated URLs. The target should check identity; use a dynamic code (see static vs dynamic) if the destination may change, and log scans where policy requires it.
- Keep it scannable for auditors. Verification workflows often mean many scans in a row; test with the QR scanner under realistic lighting before deployment.
Creating the codes themselves is straightforward — a QR URL generator for portal links, the QR generator for text payloads, and the batch QR generator for fleet-scale device labels — but the identifier strategy above should be decided with your IT and compliance team first.