For EDC

Why QR Codes and NFC Tags Fail in Emergencies

September 2026 · 4 min read

NFC tags and QR code stickers are the default answer to "how do I carry emergency info?" They're cheap, easy to set up, and they work in the demo video. But the demo video has a perfect setup: a charged phone, a working app, and a reader who knows what they're doing.

In a real emergency, at least one of those conditions is usually missing. Here's what happens when they are.

The NFC Problem

An NFC tag (Knock, TapMedID, or any of the medical NFC products) stores your info on a chip in the tag. To read it, the person holding your hand needs:

• A phone with NFC capability (most Android phones have it, most iPhones do too, but not all phones do).
• The right app installed and updated.
• Working data or Wi-Fi to load the page the tag points to (many NFC medical tags store a URL, not the data itself).
• A phone with enough battery to power NFC and load the page.

If any one of those fails, the tag is a colored square on a card. The person holding your hand has no way to read it, and they don't know that there's information on it that they can't access.

This isn't theoretical. In a car accident, the bystander who finds you might be an older person with a basic phone. In a medical event at a park, the first person to reach you might be a teenager whose phone is dead from gaming. In a disaster scenario (power outage, network down), the "URL" your NFC tag points to might not load at all.

The QR Code Problem

QR codes have the same dependency chain, plus one more: the code itself has to be scannable. And QR codes degrade.

• Wear. A QR code printed on a sticker or card loses contrast over time. Scanning a faded QR at 2am in a parking lot is a different task than scanning a crisp one in good light.
• Size. Small QR codes (the kind that fit on a credit card) are harder to scan than large ones. If the code is 15mm across, the scanner needs to be steady and close.
• Angle. QR codes are sensitive to angle. A code on a curved surface (like a sticker on a water bottle) is harder to scan than one on a flat card.
• Same phone dependency. You still need a phone with a camera, enough battery, and working data to load the URL the code points to.

The QR code also has a failure mode that NFC doesn't: if the code is partially obscured (a thumb over it, dirt on it, a crease in the card), it won't scan at all. There's no partial read. It works or it doesn't.

What "Works" Actually Looks Like

A physical ID that works in an emergency has zero dependencies. No phone. No app. No data connection. No light source (ideally). The information is readable by any human being with eyes, in any condition, without any equipment.

That means the text has to be there. Not encoded. Not stored on a chip. Not behind a URL. Just text, in a format that's readable at a glance.

This is why paramedics check for medical bracelets and cards before they look for NFC tags or QR codes. The physical format is the fallback that always works, even when the digital one doesn't.

The Middle Ground

NFC and QR codes aren't useless. They're useful as a supplement. If you have a GhostCard (or any physical ID card) in your wallet, an NFC tag on your phone case is a nice extra for the cases where someone does have a compatible phone.

But the NFC tag should never be your only emergency info. It's a backup to a backup. The primary should be something that works without any technology at all.

The Test

Here's a simple test for any emergency ID product: can a stranger read it without a phone? If the answer is no, it's not an emergency ID. It's a convenience feature that happens to be on a card.

Your emergency info should be readable by a paramedic, a teacher, a stranger at a park, or a cop in a traffic stop. All of them, without any equipment. That's the standard.