Using Wallet Passes for Healthcare: Patient ID Cards, Appointment Reminders and Loyalty

Healthcare providers deal with more patient contact than almost any other sector, and a significant portion of that contact is administrative rather than clinical. Appointment reminders, check-in processes, prescription notifications and loyalty rewards for pharmacy customers all consume staff time and patient attention. Digital wallet passes offer a practical, low-friction channel for each of these — one that patients can adopt without downloading an app, and that staff can manage without new clinical systems.

Patient ID Cards in Apple Wallet and Google Wallet

A patient ID pass in Apple Wallet or Google Wallet shows the patient's name, date of birth, NHS number and a barcode or QR code that front-desk staff can scan at check-in. The patient opens their wallet at the reception desk, the staff member scans the code and the check-in is complete — no form to fill in, no verbal spelling of surnames, no searching through a bag for a physical card.

For GP surgeries, hospital outpatient departments and minor injury units, faster check-in reduces queue times and frees receptionists for more complex queries. The QR or barcode links back to the patient record in your system, so the pass itself does not need to carry clinical data — it simply confirms identity and triggers the lookup.

Replacing a lost or expired patient ID card is instant: update the pass in the Issuepass dashboard and the patient's wallet updates automatically. There is no card to reprint and no letter to send.

Appointment Reminder Passes

Did-not-attend rates are a persistent challenge across the NHS and private healthcare alike. The standard reminder pathway — a letter, followed by a text or automated call — is effective but fragmented. A wallet pass offers a single artefact that serves as both the confirmation and the reminder.

When a patient books an appointment, issue them a wallet pass showing the date, time, location and clinician name. The pass sits in their wallet alongside their other cards. If the appointment date is approaching, the pass surfaces on the lock screen automatically — just as a flight boarding pass surfaces the morning of a flight.

If the appointment is rescheduled, update the pass and the patient receives a push notification: “Your appointment has been updated. New time: Tuesday 14 April at 10:30.” There is no need to send a new letter or SMS. The pass reflects the current booking at all times, and cancellations can trigger a pass update or removal.

For multi-site providers — private clinic groups, community health hubs — the pass can include the specific site address and a map link, reducing the number of “I went to the wrong building” calls that reception teams field.

Pharmacy Loyalty Passes

Independent pharmacies and pharmacy chains compete with supermarket dispensing services partly on convenience and partly on relationship. A loyalty pass strengthens both. Customers collect points for prescription pickups and over-the-counter purchases. When they reach a reward threshold, a push notification arrives on their lock screen: “You've earned a £5 reward. Use it on your next visit.”

The pass lives in the customer's wallet permanently. Unlike a paper stamp card (which gets lost) or a third-party loyalty app (which gets deleted), a wallet pass is part of the native phone experience. Redemption at the counter is a QR scan — quick and frictionless.

Pharmacies can also push seasonal health reminders to pass holders — flu vaccine availability in autumn, travel health services before the summer holiday season — without requiring customers to have opted in to a separate marketing list.

Data Minimisation: What Should and Should Not Appear on a Pass

The principle of data minimisation is especially important in healthcare. A wallet pass should show only what the patient or customer needs at the point of use. For a patient ID pass, that means name, date of birth, NHS number and an identifier code. It does not mean diagnoses, current medications, allergy lists or test results — these belong in a secure clinical system, not on a pass face.

The back of the pass (the detail view, not shown in the wallet list) can carry supporting information — the provider's phone number, a link to the patient portal, appointment preparation notes. Keeping sensitive detail off the front of the pass means it is not visible to anyone glancing over the patient's shoulder when they open their wallet at the reception desk.

For appointment passes, include date, time, location and clinician name. Do not include the reason for the appointment. A pass saying “Appointment with Cardiology – 14 April” discloses more than most patients would want visible on their lock screen.

GDPR, Data Storage and Device Security

A common question from healthcare IT teams is where pass data is stored and who can access it. Wallet pass data is stored on the device in the platform's wallet app (Apple Wallet or Google Wallet). It is not synced to iCloud or Google Drive backups by default — Apple explicitly excludes pass data from iCloud backups. This means the data is tied to the device and not easily recoverable by a third party.

Fields placed on the back of the pass (rather than the front) are not shown in the wallet list view and require the user to open the pass to see them. For information that should not be casually visible — a member number linked to a sensitive programme, for example — this provides an additional layer of discretion.

Under UK GDPR, you remain the data controller for any personal data held in the pass. Issuepass acts as a data processor on your behalf. We hold pass data on EU-region infrastructure, do not use it for any purpose beyond pass issuance and delivery, and provide data deletion tools in the dashboard. Any pass you revoke or delete removes the data from our systems in line with your retention policy.

For healthcare organisations implementing wallet passes, the practical approach is to treat the pass as a presentation layer — a way of surfacing an identifier or an appointment detail — rather than a data store. The authoritative record remains in your clinical or operational system. The pass simply gives the patient something to present.

Implementation Without New Clinical Systems

A concern often raised during procurement is integration complexity. The reassuring answer is that wallet passes do not need to integrate with clinical systems to deliver value. A patient ID pass can be issued from a CSV export of your patient list. An appointment reminder pass can be triggered by a webhook from your booking system or by a Zap from a Google Sheet that your admin team maintains.

For organisations with existing patient portals or practice management software, our REST API makes it straightforward to trigger pass creation at booking confirmation and pass updates at rescheduling. The integration is at the operational layer, not the clinical layer — no changes to your electronic patient record system are required.

Pharmacy loyalty passes can be managed entirely within the Issuepass dashboard for smaller operations, or via API for pharmacies with an existing EPOS system capable of sending webhook calls.

Getting Started

The fastest route is to start with a single use case — appointment reminder passes are typically the easiest to begin with, since the data is simple (date, time, location) and the benefit is immediately measurable in terms of did-not-attend rates. From there, patient ID and pharmacy loyalty are natural expansions once the team is familiar with the platform.

Start free and issue your first healthcare wallet pass today.