Can a patient wristband carry an NFC tag?

An identifier, and nothing else

No name, no date of birth, no diagnosis, no treatment, no allergy, no ward. The band carries a reference that means nothing outside the institution's own system, and everything else stays in that system behind whatever access control it already has.

This is the rule the badge data page states for staff badges and the personal data page states for tags in general. A wristband is the case where it matters most, because the wearer is identifiable by sight and cannot remove the object.

The identifier itself should not be guessable or sequential, since a number that can be incremented is a number that lets somebody ask about a patient they never met.

Anyone nearby can read it

A tag answers whoever brings a reader close enough, and a wristband spends days within reach of visitors, other patients, and anyone walking past a bed. Nothing about the tag distinguishes an authorised reader from a curious one, and the tracking page sets out what that does and does not allow.

What protects the person is therefore not the tag but what the identifier reveals, which is nothing, and what the service behind it will answer, which is nothing without credentials.

It is also worth remembering that nobody can tell what a tag holds by looking at it, as the contents page explains, so a band that does carry readable data gives no sign of it. That cuts both ways, and it is an argument for auditing what is actually written rather than trusting a specification.

What a tap proves

That a band was presented to a reader. Not who is wearing it, not that it is on the right wrist, and not that it was never swapped, which the credential page explains for every plain tag.

How a patient is identified before anything is done to them is a clinical procedure, set by the institution and by the rules that apply to it, and this page does not describe or replace it. A tag can make a record easier to find; the identification itself is not a technical question.

Treat the tap as a convenience that removes typing, and design every process on the assumption that the tap can be wrong.

The band as an object

It is worn for days, gets wet, is taped over, is slept on, and is cut off at the end. It sits against skin the whole time, which makes the material and the edges a comfort question before they are a technical one, and the wearables page covers what that does to antennas and read distance.

Keep the printed information primary. A band whose text is legible works when a phone is flat, when the tag has failed, and for everyone who never taps it, which is the same conclusion the inspection page reaches from a regulation rather than from convenience.

And plan for the band being replaced: a new band means a new tag and a new identifier, so the mapping in the system has to accept a change of band without losing the record, which is a database question that has to be answered before any of this is ordered.