From Wristband to Digital Token
How the hospital wristband could unlock safer access, authentication, and digital health adoption
For decades, the hospital wristband has been treated as a printed identity check.
It carries the patient’s name.
It carries a date of birth.
t may carry a medical record number, barcode, QR code, or visual alert.
It gives staff something to read, scan, confirm, or compare before care is delivered.
That role still matters. The wristband remains one of the most practical identity tools in health care. It is visible, it is familiar, itt works across departments, and itt follows the patient from registration to bedside, from imaging to pharmacy, from procedure to discharge, but the wristband is usually treated as passive. Low tech we often take for granted.
It waits to be read.
It waits to be scanned.
It waits for a staff member to initiate the identity check.
That is useful, but limited. The next opportunity is to see the wristband differently.
Not just as a printed label.
Not just as a scannable identifier.
Not just as a way for staff to confirm who a patient is.
The wristband can become a temporary digital identity token – Not a token that stores more personal health information on the band itself. That would create new privacy and security risks. The better model is different.
The wristband becomes a trusted starting point.
It can initiate a secure workflow.
It can confirm that the patient is physically present.
It can connect the patient to a specific care episode.
It can support two-factor or step-up verification.
It can help the patient unlock the right digital service at the right time.
It can allow sensitive information to be collected directly from the patient, instead of being passed through staff who do not need it.
That is a different way of thinking about identity. Today, the wristband helps the system identify the patient. Tomorrow, the wristband could help the patient authenticate into the system.
The problem is no longer only identification
Most wristband workflows focus on one question: “Is this the right patient?” That question is essential. It sits at the centre of medication safety, specimen collection, imaging, transport, procedures, documentation, and discharge. However, modern health care increasingly depends on another question:
"Can this patient securely access & easily our digital tools or required workflow?”
That workflow might be a hospital patient portal.
It might be a provincial or national health portal.
It might be remote patient monitoring.
It might be a virtual ward.
It might be hospital-at-home.
It might be a discharge pathway.
It might be a consent process.
It might be caregiver access.
It might be delivery of medical equipment.
It might be post-surgical patient-reported outcomes.
In each case, the issue is not only identity at the bedside. It is identity across the next step in the journey. This is where many digital health workflows lose momentum.
The patient is already in the hospital or clinic.
The organization has already identified them.
The patient is wearing a wristband.
The care team knows which encounter they are attached to.
The patient may be about to receive results, instructions, follow-up appointments, prescriptions, referrals, remote monitoring equipment, or home care.
But then the workflow often becomes manual.
Someone has to collect an email address.
Someone has to confirm a mobile number.
Someone has to enter a home address.
Someone has to invite the patient to a portal.
Someone has to explain how to register later.
Someone has to onboard the patient into another system.
Someone has to troubleshoot when the patient never activates the service.
This is where adoption breaks down, not because the technology does not exist, but because the identity workflow is not simple enough.
From label to token
A label is read.
A token is used.
A label says, “This is the identifier printed here.”
A token says, “This is an active, trusted, time-limited identity relationship that can initiate a secure action.”
That distinction matters. The wristband does not need to become a database. It does not need to expose more information. It does not need to become a master key. It simply needs to become a safer bridge between the physical patient and the digital workflow.
In a token model, the wristband can launch an approved workflow, but the workflow still decides what level of assurance is required.
A low-risk interaction may only require the wristband scan and basic confirmation.
A higher-risk interaction may require two-factor authentication.
A very sensitive interaction may require step-up verification, patient consent, staff-assisted confirmation, or connection to a government-issued digital health identity.
The wristband becomes the starting point, not the whole security model. That is the future- facing idea, not more information printed on the wristband – more intelligence behind the wristband.
The hospital is an identity moment
Hospitals often think about wristbands as safety devices, which they are, but they are also identity moments. Every admission, emergency visit, procedure, clinic appointment, discharge, remote monitoring referral, or virtual care transition creates a moment where the patient is physically present, clinically known, and already connected to a trusted encounter.
That moment has enormous value.
It is much stronger than asking the patient to go home, find a website, enter a code, remember an email, create an account, verify themselves later, and hope the process works.
At the point of care, the patient has context. They have a reason to act. They know why the workflow matters. Staff can explain the value. The wristband can initiate the process. The system can connect the action to a real encounter.
That is why the wristband token is not just an identity idea. It is an adoption idea.
Health systems do not only need digital tools. They need better ways to get patients into those tools at the moment they are most relevant – at the beginning of their health journey.
Government health portals: a powerful use case
One of the strongest use cases for the wristband token is onboarding patients into regional, provincial, or national health portals.
Many countries and health authorities are moving toward patient-facing digital health records. In Canada, the federal government has framed connected care around secure access to personal health information and better sharing between health systems. In February 2026, Health Canada described the Connected Care for Canadians Act as part of a plan to help systems connect and give Canadians more control over their health data, while respecting privacy legislation. (Canada)
Ontario is a useful example.
Ontario Health says it is advancing secure and convenient access to digital health tools for Ontarians. It describes My Ontario Account for Health as a service that helps people prove who they are using their Ontario health card so they can safely see their health records and use other Government of Ontario online health tools. (Ontario Health)
Ontario Health also describes its role in digital health identifier activities, including validating a health card number, verifying that the individual is who they say they are, creating or renewing a digital health identifier, authenticating access to digital health tools, and managing activation, deactivation, reactivation, or disposal of that identifier. (Ontario Health)
That creates a practical question:
Where is the best moment to help a patient activate access to a government health portal The answer is not later at home. It is while the patient is already in care.
The patient is physically present.
They have already been identified.
They are wearing an active wristband.
They are connected to a real hospital encounter.
They may be receiving results, discharge instructions, referrals, prescriptions, follow-up appointments, or remote monitoring equipment.
They have an immediate reason to want access to their health information.
The wristband token could become the bridge.
The patient scans the wristband-linked code.
The system confirms the wristband is active for that encounter.
The patient is directed to the approved government health portal workflow.
They complete the required identity verification.
They connect their health card or government identity credential and hospital record.
They complete two-factor authentication.
They activate access to their broader health record.
The hospital does not become the government identity provider, the wristband does not store government health data. The token simply creates a trusted, time-limited path from the hospital encounter to the public digital health identity workflow.
That matters because adoption remains a challenge. CIHI has reported that Canadians want connected electronic health information, but access and use are still uneven. Its 2024 shared priorities reporting notes that 4 in 5 Canadians were interested in accessing personal health information, while only 2 in 5 had actually done so, based on 2023 survey data. (CIHI)
A hospital wristband token could help close that gap. It could turn a hospital visit into the activation moment for broader digital health participation.
Patient portals: removing the activation barrier
The same principle applies to hospital patient portals. Patient portals often fail at the point of activation.
The patient is told to go home and register.
They are given a code.
They receive an email.
They forget.
They lose the instructions.
They do not recognize the sender.
They become uncertain about whether the portal is legitimate.
They call for help later, or they never activate at all.
But during the care encounter, the organization already has a powerful identity moment.
The patient is present.
The wristband is active.
The encounter is known.
The care team can explain the value of access.
The patient has a reason to complete the process now.
A wristband token can turn that moment into a portal activation workflow.
The patient scans.
The system verifies the wristband token.
The patient completes two-factor authentication.
They create or connect their portal account.
They confirm communication preferences.
They can invite a caregiver if appropriate.
They leave with access already working.
This changes the portal from something the patient is asked to do later into something they complete as part of care. That is how digital adoption improves. Not by telling patients one more time that the portal exists. By removing the identity and onboarding barriers that stop them from using it.
Medirex mySPOT Onboarding: moving the right task to the right person
Remote patient monitoring is another clear example.
RPM programs often need information that is essential to the program but not always essential for every staff member to handle manually.
The program may need the patient’s mobile number.
It may need an email address.
It may need a shipping address.
It may need delivery instructions.
It may need caregiver contact details.
It may need device setup preferences.
It may need consent to communicate.
It may need confirmation that the patient understands what equipment is coming and what to do when it arrives.
In many organizations, this becomes staff work. A nurse, coordinator, or clerk collects the information. They enter it into another system, they correct errors, they follow up when activation fails, and they become the bridge between the patient and a digital service they may not directly manage.
That creates friction. It also creates unnecessary exposure to information that staff may not need for their role. Ontario’s Personal Health Information Protection Act states that a health information custodian shall not collect, use, or disclose more personal health information than is reasonably necessary to meet the purpose of the collection, use, or disclosure. (ontario.ca) That principle is directly relevant to workflow design.
A Medirex Onboarding workflow can be framed differently.
The wristband token launches the onboarding process.
The system confirms this is an active, eligible patient encounter.
The patient completes identity verification.
The patient enters their own phone, email, address, delivery instructions, caregiver details, and communication preferences.
The RPM system receives the information it needs.
The clinical team sees completion status, readiness, and exceptions.
The nurse does not need to become a data-entry clerk. The coordinator does not need to manually retype information the patient can provide directly. The staff member does not need broad access to personal contact and delivery data if their role only requires knowing whether onboarding is complete.
The patient is the best source for contact details, delivery instructions, caregiver information, and communication preferences. The care team is the best source for clinical eligibility, escalation rules, and care decisions. The wristband token connects the two.
That is the productivity gain and it is not about replacing staff. It is about removing avoidable administrative work from clinical workflows.
The wristband as a privacy-preserving bridge
A wristband token should not expose more information. It should expose less. The token does not need to say, “Here is everything about this patient.” It should say, “This is an active patient identity for this care episode, and this person is eligible to complete this specific workflow.”
That difference matters.
In the old model, staff may have to collect, view, copy, type, or transfer information because the workflow depends on them. In the token model, the patient can provide sensitive information directly into the system that needs it.
The staff member sees what they need to act safely.
The receiving system gets what it needs to complete the workflow.
The organization gets an audit trail.
The patient gets a smoother experience.
Privacy improves because unnecessary handling is reduced.
Productivity improves because manual data entry is reduced.
Adoption improves because the patient completes the workflow while the need is immediate and the identity context is strong.
Other workflows this could unlock
Once the wristband is understood as a digital token, the possibilities expand.
A discharge workflow could allow the patient to confirm identity, access instructions, choose a pharmacy, invite a caregiver, complete education, and receive follow-up reminders.
A hospital-at-home workflow could allow the patient to confirm address, caregiver support, equipment delivery details, virtual visit preferences, and escalation instructions.
A virtual ward workflow could connect inpatient care to remote monitoring without starting identity verification from scratch.
A consent workflow could allow a patient to review material, ask questions, complete step-up verification, and sign only after the identity and consent context are clear.
A caregiver access workflow could allow the patient to authorize a family member or substitute decision-maker for specific information or communication, rather than relying on informal phone calls, handwritten notes, or unclear verbal permission.
A patient-reported outcomes workflow could allow the patient to complete symptom surveys, recovery forms, wound checks, pain scores, or therapy updates under a verified identity.
A device loan workflow could support equipment tracking, delivery, setup, troubleshooting, and return.
An identity recovery workflow could help patients regain portal access while they are physically present and already identified, instead of relying entirely on remote help desk processes later.
A government health portal workflow could help the patient activate access to their broader provincial, regional, or national record before they leave the hospital.
These are not just technology ideas. They are workflow ideas.
Every time the patient can securely complete the information only they know, staff are freed from avoidable data entry.
Every time the system can verify identity at the point of workflow, adoption becomes easier.
Every time access is scoped to a specific purpose, privacy improves.
Every time the token creates an audit trail, the organization gains visibility into where onboarding succeeds, where it fails, and where staff are forced to compensate.
The token should not be a master key
This is the most important design principle. The wristband token should not unlock everything.
It should not become a broad access pass.
It should not store unnecessary patient information.
It should not allow anyone with the band to access sensitive records.
It should not bypass proper consent, authentication, or governance.
The wristband should initiate a workflow. The workflow should determine what happens next. That means the token must be scoped.
It should be tied to a specific encounter.
It should be time-limited.
It should be revocable.
It should only open approved workflows.
It should support step-up verification.
It should create an audit trail.
It should expire when the encounter or use case ends.
It should have an exception process when the patient cannot participate.
A low-risk workflow might only require a scan and confirmation. A higher-risk workflow might require a one-time code, portal login, government identity credential, staff-assisted verification, or caregiver validation. A sensitive workflow might require explicit consent and additional authentication.
The wristband is the doorbell, not the house key. It signals that the patient is present and connected to a trusted encounter. The rest of the system decides what level of proof is required before access is granted.
The patient becomes an active participant
The earlier idea in this series was that the patient is often the missing identity factor. The wristband token gives that idea a practical workflow. The patient is no longer only the person being identified by others. They become an active participant in identity assurance.
They can confirm who they are.
They can choose how they want to be contacted.
They can enter the information only they know.
They can activate access to their records.
They can invite a caregiver.
They can complete onboarding for remote care.
They can identify when something does not look right.
This does not shift responsibility away from the health system. The organization remains responsible for safe identification, secure access, privacy, consent, and workflow design.
But it recognizes something important: Patients are often the best source of truth for the details that make digital care work.
Their phone number.
Their email.
Their address.
Their delivery instructions.
Their caregiver.
Their preferred language.
Their communication preferences.
Their ability to access a device.
Their willingness to participate in remote monitoring.
Their readiness to use a portal.
When staff collect all of that manually, errors and delays are predictable. When patients can provide it directly through a secure, identity-assured workflow, the process becomes cleaner.
The real opportunity is adoption
Digital health adoption is often treated as a communication problem.
Patients need more instructions.
Patients need more reminders.
Patients need more education.
Patients need another brochure, another email, another link.
Sometimes that is true. Often the problem is not awareness.
The problem is friction.
The patient is asked to activate access after the moment has passed. They are asked to verify identity without context. They are asked to create an account when they are tired, overwhelmed, or already home. They are asked to enter information into systems they do not recognize. They are asked to trust a digital workflow that feels disconnected from the care they just received.
The wristband token can reduce that friction.
It connects the digital workflow to the physical care moment.
It makes onboarding feel like part of care, not an administrative afterthought.
It gives staff a simple way to say, “Scan your wristband and complete this secure step now.”
It gives patients a clear reason to act.
It gives the organization a stronger audit trail.
And it gives digital health programs a better chance of actually being used.
From barcode to behaviour
The barcode tells the hospital system who the wristband belongs to.
The digital token can do more.
It can help the patient prove they are the right person.
It can launch hospital workflows.
It can support two-factor verification.
It can simplify patient portal activation.
It can reduce staff data entry for RPM and home-based care.
It can protect sensitive contact, delivery, and caregiver information.
It can help patients activate access to provincial, regional, or national health portals.
It can turn a hospital encounter into the starting point for broader digital health participation.
That is the next step in patient identity. The wristband remains physical, but the workflow around it becomes digital, governed, and interactive.
The future wristband is not a database. It is not a master key. It is not a replacement for clinical judgment, consent, government identity systems, or privacy law. It is a trusted, temporary token that helps the right patient enter the right workflow at the right time.
That is how health systems can move beyond asking:
“Did we scan the band?”
Toward a better question:
“Did we use identity to make the next step safer, easier, and more trusted?”
About Medirex Systems Inc.
Medirex Systems Inc. (Medirex) is a Canadian-owned and operated business connecting patients to health information systems. Being an industry leader for over 50 years, Medirex has evolved to bridge the gap between patient identification and engagement by cultivating patient connections with ease, security, and no errors. Providing a positive patient identification experience for over 10 million Canadians, Medirex adopts technologies ensuring that the patient has a voice in their healthcare journey. Medirex aids in the adoption of digital health resources and data to improve the patient experience for your healthcare organization.
Media Contact:
Medirex Communications
Medirex Systems Inc.
+1.416.363.9313
info@medirex.com