Data protection

Smartcards, passwords and shared logins

Why sharing NHS smartcards and logins in a GP practice is a breach, the real reasons staff do it, and practical fixes for reception, locums and leavers.

Ava research teamPublished 6 min read

On this page
  1. What a smartcard actually does
  2. The legal and professional risk
  3. Why staff share, and what to do about it
  4. Passwords and multi-factor authentication
  5. An access audit you can do this month
  6. Remote working and personal devices
  7. When you suspect misuse
  8. Example: the locum's first morning
  9. What to say when someone asks to borrow a card
  10. Frequently asked questions
  11. References

Key takeaways

  • A smartcard or login identifies one person; every action taken with it is recorded against them, whoever was at the keyboard.
  • Sharing removes the audit trail, breaks need-to-know access and can expose the person who shared to disciplinary and legal risk.
  • Staff share for practical reasons, such as slow log-ons, missing cards for locums and too few card readers, so fix those causes.
  • Multi-factor authentication on remote accounts and same-day removal of leavers' access are basic toolkit expectations.

What a smartcard actually does

An NHS smartcard, with its passcode, proves to national and local systems that the person using it is who they say they are and has the access their role allows. It controls what a user can see in the clinical record, which national services they can use and what they can sign. Every view, edit and prescription made with the card is recorded against its holder.

That makes sharing a serious problem, not a technicality. The Caldicott Principles say access to confidential information should be on a strict need-to-know basis[1]. When a receptionist works under a GP's card, or a locum uses a partner's login, the system shows the wrong person, sees the wrong access level and cannot reconstruct who looked at what. If someone is later accused of inappropriate access, nobody can prove who it was.

Under section 170 of the Data Protection Act 2018, it is an offence for a person knowingly or recklessly to obtain or disclose personal data without the consent of the controller, or to procure its disclosure to another person[2]. A member of staff who lends their card to someone without the right access, or who uses another person's card to look at records outside their role, can fall within it. Professional regulators treat misuse of access seriously too.

For the practice, shared access undermines the security of processing that UK GDPR requires, and serious infringements can attract fines of up to £17.5 million or 4% of turnover[3]. More often the consequence is an employment dispute or a patient complaint the practice cannot investigate properly because the audit trail is useless.

A useful line for staff: ‘Your card is your signature. Lending it is signing a blank page.’

Why staff share, and what to do about it

Common reasons for sharing smartcards or logins, with fixes.
Reason staff givePractical fix
Logging in takes too long at a busy front deskFast user switching or session tap-in so each person can take over a PC in seconds
A new starter or locum has no card yetRequest cards through the registration authority before the start date; build it into the onboarding checklist
Too few card readersCount readers against staff on shift and buy more; they cost far less than an investigation
The card is left in the PC for the whole sessionCard-removal locks the screen; teach staff to take the card with them every time they stand up
Someone needs access their role does not haveRequest a role change formally rather than borrowing a colleague's card
The shared login is for a system that does not support individual accountsAsk the supplier for named accounts; if impossible, record who used it and when

Passwords and multi-factor authentication

Smartcards cover national systems, but practices also use email, cloud storage, telephony portals, online consultation tools and private clinic software with ordinary logins. The 2026-27 Data Security and Protection Toolkit asks GP practices to use multi-factor authentication on all remotely accessible user accounts, with exceptions only as approved by senior management, and to have a reliable way of removing or amending people's access when they leave or change role[4].

UK businesses with any two-factor authentication requirement, 2025
UK businesses with any two-factor authentication requirement, 2025Donut chart. Require two-factor authentication: 40%.Require two-factor authentication: 40%40%
  • Require two-factor authentication 40%

Source: GOV.UK (Department for Science, Innovation and Technology), 2025[5]

Show the data
ItemValue
Require two-factor authentication40%

Many organisations have not got there. In 2025 only 40% of UK businesses had any requirement for two-factor authentication[5]. Start with the accounts that matter most: email, any system reachable from outside the practice network, and admin accounts for telephony and IT.

  • Use long passphrases rather than complex short passwords, and never reuse a work password elsewhere.
  • Turn on multi-factor authentication for email and cloud services first, then supplier portals.
  • Change default passwords on routers, phones and admin portals as soon as equipment is installed.
  • Use a password manager for shared service accounts that genuinely cannot be individual, with access limited to named people.

An access audit you can do this month

  1. List every system

    Clinical system, smartcard roles, email, telephony portal, online consultation, document management, private clinic software, website admin and banking.

  2. List every account on each

    Export user lists from each system and compare them with your staff list, including locums and people on long-term leave.

  3. Remove or disable leavers

    Any account belonging to someone who has left should be disabled today, and smartcard roles removed through the registration authority.

  4. Find shared and generic accounts

    Look for names like reception, admin or locum. Replace each with named accounts or document why it must remain shared.

  5. Check access levels

    Confirm each role sees only what it needs: reception rarely needs full clinical record access, and former partners should not keep admin rights.

  6. Set a review date

    Repeat quarterly, and run a quick check on the day anyone leaves.

Remote working and personal devices

Clinicians and managers increasingly work from home, from a branch site or from their phone between sessions. Each of those routes is an account that can be shared or stolen. Remote access to clinical systems should run through the practice's approved route, with smartcard or equivalent authentication, never through someone else's session left open at the surgery.

  • Do not save practice passwords in a personal browser on a family computer.
  • Lock any device used for work with a PIN or biometrics, and set it to lock automatically after a short time.
  • Keep work email on personal phones inside a managed app that the practice can wipe if the phone is lost.
  • Do not let family members use a device while it is logged in to work systems.
  • Report a lost card, phone or laptop the same day so access can be suspended.

When you suspect misuse

Sooner or later, an audit or a complaint will suggest that someone looked at a record they had no reason to see, or used someone else's access. Handle it as a structured investigation, not a conversation in the corridor.

  1. Secure the evidence

    Ask the system supplier or your IT provider for the audit log for the record and the account concerned, covering the relevant dates.

  2. Establish the facts

    Compare the log with rotas, appointment lists and any legitimate reason for access, such as a task, a letter or a phone call.

  3. Decide whether it is a breach

    Involve your information governance lead or data protection officer; inappropriate access to a record is a personal data breach that must be logged and may need reporting.

  4. Follow your HR process

    Interview the people involved with HR advice, and keep the investigation separate from the decision about any sanction.

  5. Tell the patient where appropriate

    If a patient's record was accessed without a legitimate reason, they should usually be told, with an apology and an explanation of what you have done.

Example: the locum's first morning

Example: a locum GP arrives at Elm Tree Practice, a fictional surgery, and finds that her smartcard has not been given access to the practice's organisation code. The duty partner offers to log her in on his card so she can start her list. The practice manager stops this, calls the local registration authority, and arranges temporary access within the hour; in the meantime the locum takes telephone consultations that the partner documents under his own login.

Example: the manager adds a step to the locum booking form: confirm the locum's smartcard number and request the access two working days before the first session. Shared-card offers stop because the problem that caused them has gone.

What to say when someone asks to borrow a card

Staff need a polite, ready answer, especially when the person asking is senior. A script helps: ‘I can't lend my card, because everything done on it is recorded as me. Let me log you in on your own account, or I'll do that task for you now under my own login and note that it was at your request.’ Back staff who use it. A partner who insists on borrowing a card is creating the risk, not the receptionist who refuses.

Access control is one strand of the practice's wider security. See phishing training for the attacks that steal passwords, ransomware preparedness for what happens when they succeed, and WhatsApp in clinical settings for the workarounds staff reach for when official systems are slow. Network access for these systems is covered in HSCN connectivity.

Frequently asked questions

Is sharing an NHS smartcard a data breach?

It breaks need-to-know access and the audit trail, and using or lending access without the controller's consent can be an offence under section 170 of the Data Protection Act 2018[2]. Treat it as a security incident.

Can a receptionist use a GP's card to issue a prescription?

No. Prescriptions must be issued under the identity of the authorised prescriber who made the decision.

What should we do when a member of staff leaves?

Disable all their accounts that day and remove smartcard roles through the registration authority; the toolkit expects a reliable leavers process[4].

Do we need multi-factor authentication?

For GP practices, the toolkit asks for it on all remotely accessible accounts, with exceptions approved by senior management[4].

References

  1. GOV.UK (National Data Guardian) (2020). The Caldicott Principles (opens in a new tab) ↑

  2. legislation.gov.uk (The National Archives) (2018). Data Protection Act 2018, section 170: Unlawful obtaining etc of personal data (opens in a new tab) ↑

  3. legislation.gov.uk (The National Archives) (2026). UK GDPR Article 83: General conditions for imposing administrative fines (opens in a new tab) ↑

  4. NHS England (Data Security and Protection Toolkit) (2026). Outcomes, assertions and evidence items for the Data Security and Protection Toolkit 2026-27 version 9 (opens in a new tab) ↑

  5. GOV.UK (Department for Science, Innovation and Technology) (2025). Cyber security breaches survey 2025 (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo