Clinicians should be caring for patients, not resetting passwords.
A shift can start with a dozen sign-ins: clinical records, prescribing, rotas, e-learning and admin systems, some of them Windows software older than the people using it. My1Login signs your clinical and office workforce in to all of them, and keeps patient data behind passwords nobody can phish.
- Every system, including legacy clinical software
- Passwords hidden, so there is nothing to phish
- Every access to patient systems logged
| App | Type | Status |
|---|---|---|
| Clinical record system | Windows desktop | Signed in |
| Prescribing | Web | Signed in |
| Rota and handover | Cloud | Signed in |
| E-learning portal | Web · code generated + filled | Signed in |
Trusted in health and care by
Every minute spent signing in is a minute away from a patient.
Healthcare runs on more systems than almost any other sector, used by people who move between wards, sites and shifts. Passwords get forgotten, written down and shared, and each one is a way in for attackers.
Sign-ins that eat into care
Separate logins for clinical, prescribing, rota and admin systems, and a forgotten password means a lock-out and a reset mid-shift.
What it leads to: delays before patients are seen, and a busy service desk.
Older systems single sign-on can't reach
Many clinical and back-office applications are Windows desktop software with no modern sign-in, so they sit outside single sign-on.
What it leads to: separate passwords that get written down or reused.
Phishing aimed at clinicians
Fake rota changes, test results and IT notices are written to be clicked. One typed password can open patient records.
What it leads to: breach investigations and reports to the ICO.
One sign-in to every clinical and admin system.
Your workforce signs in to Windows as usual. My1Login takes it from there, for every kind of app, and IT can see every access.
Sign in once
Signing in to the directory signs clinicians in to My1Login too. From then on, every system opens already signed in.
Every system covered
Web, cloud and Windows desktop clinical software, with no API needed, and the one-time codes some systems ask for generated and filled in.
Access you can show
Every access to patient systems is recorded, ready for your Data Security and Protection Toolkit submission or an investigation.
More clinical capacity for the patients who need to be seen.
On what My1Login has changed for LCW's clinicians:
"It's improving patient outcomes because we're getting more clinical capacity to patients that need to be seen."
"…the deployment of My1Login's IAM solution, thus improving security and enabling the healthcare provider to offer more efficient and faster care to patients."
- 4.6 millioncitizens served by LCW's urgent care
- 100%adoption, guaranteed
More stories
Evidence for the assurance healthcare is held to.
Organizations with access to NHS patient data have to show who can reach it and how it is protected. My1Login gives you the controls and the records.
| Framework | What it expects of access | How My1Login helps |
|---|---|---|
| NHS Data Security and Protection Toolkit (DSPT) | Show that access to patient data is limited to the right people, managed through joiners and leavers, and protected with strong authentication. | Access granted from your directory, unique strong passwords hidden from users, MFA on the systems that need it, and an audit trail of every access. |
| Cyber Assessment Framework (CAF) | The DSPT is moving to CAF-aligned assessment for many NHS organizations; objective B2 covers identity and access control. | Evidence for B2: who can access which systems, how they authenticate, and when access was removed. |
| UK GDPR | Health data is special category data, and needs appropriate technical measures, including access control. | Zero-knowledge encryption, so nobody outside your organization can read stored credentials, including My1Login. |
| Cyber Essentials and Cyber Essentials Plus | User access control, including strong passwords or MFA on every account. | Password policies enforced on every account, and MFA per app. |
| ISO/IEC 27001 (yours) | Controls over who can access what, how they authenticate, and a record of access. | Governance of access to every system and a full audit trail, as evidence for your own certification. |
Built for the way healthcare works.
Everything below works across web, cloud and Windows desktop systems.
Legacy clinical software
Windows desktop applications are covered without an API, including in-house and older systems.
One-time codes, generated and filled
Systems that ask for an authenticator code get it generated and filled in, so nobody reaches for a phone.
Locum and agency access
Give temporary clinicians access for the dates they work, and it ends automatically.
Leavers, in one step
Remove someone from the directory and their access to every system goes with them.
Passwords nobody sees
Nothing for a phishing email to collect, and nothing for a leaver to take away.
Shadow IT found
My1Login spots sign-ins to apps IT didn't know about, so they come under the same rules.
Zero-knowledge encryption
The keys stay inside your network. Nobody outside it can read your stored credentials, including us.
UK-based team
Deployment and support from the people who build My1Login, headquartered in London.
Healthcare reading
Healthcare questions
Does it work with older clinical systems?
Yes. My1Login covers web, cloud and Windows desktop applications, including older and in-house software with no modern sign-in and no API.
Can locum and agency clinicians have temporary access?
Yes. Share access for set dates, days or hours, and it ends automatically when their placement does.
Can My1Login see patient data?
No. My1Login manages sign-ins, not clinical records, and with zero-knowledge encryption nobody outside your organization can read the stored credentials, including My1Login.
How does it help with the Data Security and Protection Toolkit?
It gives you controls and records for access: who can reach which systems, how they authenticate, and an audit trail of every access, to support your submission.
How long does it take to deploy?
At Natural Power and ELEXON, the first user was up and running in less than an hour. The full rollout depends on how many systems you bring in.
Bring your most awkward clinical system to a 5-minute demo.
We'll sign in to it without a password, with the one-time code generated and filled in, and show you the record of who opened it.
- 5 minutes, on your own apps
- A specialist replies within one working day
- No obligation