Learn from patient safety events (LFPSE) service account types and who they are for
In most large provider organisations, such as NHS trusts, staff will continue to record patient safety events on to their organisation’s local risk management system (LRMS) which will then upload directly to the new national Learn from patient safety events (LFPSE) service – once local systems have been upgraded to LFPSE compliant software.
Organisations without a LRMS, and their staff, will need to register for a LFPSE account before they can access the system and begin to record patient safety events. This is done via the Learn from patient safety events online service.
There are four main external user account types in the LFPSE web application, which each allow the user different privileges relating to what data they can record and/or edit, and what data they can access to view.
Once registered, you will be able to request upgrades to your account type. To help you chose the right one, we have listed details of each account type below.
Account type summaries
Account type | Summary | Access to records on the online service | Access controls |
Standard | A standard account is suitable for the majority of users, and provides the ability to:
|
Only has access to records they themselves have created.
Free text is scanned and PII removed before it is made available to the user. |
Users applying with an nhs.net email address are auto-approved for the organisation they are registered with in NHS England Applications (Okta) and any organisations they add within the LFPSE web application.
Users applying from other email domains need to be approved by Super Admins (NHSE internal team). |
Organisational | An organisational account is suitable for users who have responsibilities for reviewing, updating or overseeing patient safety events completed by any user within their organisation. These are likely to be individuals working in the patient safety or risk management teams, where they exist, or other individuals with responsibilities for monitoring or responding to patient safety events in their organisation or wider area of responsibility, or quality assuring the information provided by the people creating the initial records.
An organisational account provides the same abilities as a standard account, plus the ability to:
|
Has access to records they themselves have created. Free text is scanned and PII removed before it is made available to the user.
Read/write access to the main details of any record created from within their registered organisation(s), read-only access to the Statutory and National Policy Information, and read-only access to their child organisations’ records*.
Free text is scanned and PII removed before it is made available to the user.
The name and the organisation of the user who created the record is visible, unless they have recorded anonymously. |
A Standard user can apply for an Organisational account and the request will be approved or rejected by the local admin user. If no local Admin is yet assigned, the user is informed to contact their organisation to allocate an admin user or request to be an admin user themselves. |
Admin | Admin accounts have the widest access to functions and responsibility within the system. Admin accounts are designed to be used by people within an organisation who have responsibilities for the highest level of oversight of patient safety events, including the authorisation to declare Never Events and Serious Incidents, responsibility for ensuring statutory reporting requirements are met, and the ability to approve account access for other users within their organisation or patch.
An admin account provides the same abilities as an organisational account, plus the ability to:
|
Has access to records they themselves have created. Free text is scanned and PII removed before it is made available to the user.
Read/write access to the full details of any record created from within their registered organisation(s), including the ability to complete or amend the Statutory and National Policy Information, and read-only access to their child organisations’ records.
Free text is scanned and PII removed before it is made available to the user.
The name and organisation of the user who created the record is visible unless they have recorded it anonymously. |
A Standard or Organisational user can apply for an Admin account.
If their organisation has a nominated Admin, the request will be approved/rejected by them.
If no local Admin is yet assigned, it can be approved or rejected by Super Admins. |
“Commissioner – read only”*
(Organisational accounts for ICBs, and Admin accounts for ICBs) |
With the advent of ICBs and their evolving commissioning roles, LFPSE has an organisational or admin user type specifically for ICBs. The only difference with these account types is that it is read-only access. | As well as access to their own ICB’s data, organisational and admin users from ICBs have automatic read-only access to the records relating to organisations they commission (e.g. primary care). | This is controlled by the LFPSE ‘parent/child’ hierarchical data supplied by ODS (at the moment this is limited to GP practice/ICB only, this may extend as the ODS hierarchical data evolves). ICBs can also request read-only access to an organisation’s data within the system (e.g. where commissioners have direct commissioning contracts), where the child organisation can approve/reject their access. |
Super Admin | Super Admins sit within the National NHSE Patient Safety team, with operational responsibility for the LFPSE service. They can delegate permissions within internal NHSE apps, as well supporting provider and commissioner user permissions. | This varies by post. Some users with responsibilities for e.g. Quality Assurance or Clinical Review will have full access to all LFPSE data via internal LFPSE tools (Anonymisation App; National Review Deep Dive tool). | Super admin users can approve other super admin users within the national patient safety team. However super admins cannot alter their own permissions. |
Full account type permissions
The table below summarises the full list of activities each account type can perform, including accessing data, editing rights and fulfilment of governance activities.
User type | ||||||
Anonymous | Standard | Provider Organisational | Provider Admin | *”Commissioner” | ||
ICB Organisational | ICB
Admin |
|||||
Record an event Anonymously | Yes | Yes | Yes | Yes | Yes | Yes |
Save a draft | Yes | Yes | Yes | Yes | Yes | |
Record an event as a logged-in user | Yes | Yes | Yes | Yes | Yes | |
View my submitted events | Yes | Yes | Yes | Yes | Yes | |
Update my submitted events | Yes | Yes | Yes | Yes | Yes | |
Mark my submitted events as ‘reviewed’ | Yes | Yes | Yes | Yes | ||
Complete/edit statutory and national policy requirements for my events | Yes | Yes | ||||
View individual submitted events from across my organisation | Yes | Yes | Yes | Yes | ||
Update an event from my organisation | Yes | Yes | Yes | Yes | ||
Mark an event as ‘reviewed’ from across my organisation | Yes | Yes | Yes | Yes | ||
Complete/edit statutory and national policy requirements for my organisation’s events | Yes | Yes | ||||
View statutory and national policy requirements for my organisation’s events | Yes | Yes | Yes | Yes | ||
View individual submitted events from my child organisations | Yes | Yes | ||||
View statutory and national policy requirements for events from my child organisations | Yes | Yes | ||||
Approve enhanced user (organisational/admin) requests for my organisation | Yes | Yes | ||||
Reject enhanced user (organisational/admin) requests for my organisation | Yes | Yes | ||||
Revoke enhanced user access to my organisation | Yes | Yes |
These arrangements will be kept under review with users to ensure they are appropriate and fit for purpose.
Future Plans
LFPSE has now launched its Data Access Application. Further user research is being undertaken to establish the full permissions for the aggregated reports including the ability to extract/download the data and where appropriate, access to individual records from sub-group analyses.