There are 7 steps to set up LFPSE reporting within your Radar Healthcare system:
Find more information on each step below…
1. Register for an LFPSE Account
Register for at least 1 admin user account at https://psims-prd.developer.azure-api.net/signup.
This account is required to be able to submit LFPSE data to NHS England.
Please see the guide at the bottom of this article for instructions on how to register for an account. This guide also includes information on how to get your API key which is required just before you go live with LFPSE reporting.
2. Share your ODS Code(s) with Radar
Reach out to your main contact at Radar Healthcare or submit a ticket to our Support team (support@radarhealthcare.com) to let us know:
- You’re interested in setting up LFPSE reporting in your system
- Your organisation’s ODS code(s)
It is important to let us know if you have 1 ODS code or multiple ODS codes as this can affect the setup of your Locations.
ODS code(s) can be found via this website: https://odsportal.digital.nhs.uk/Organisation/Search
What is an ODS Code?
ODS Codes are required for healthcare providers to gain access to certain NHS services. If you don’t have an ODS code these are created by Organisation Data Service within NHS Digital. More info here: https://digital.nhs.uk/data-and-information/data-collections-and-data-sets/data-sets/mental-health-services-data-set/submission-guidance/registration
3. Confirm your Radar LFPSE setup
Once we’ve received your ODS code, we’ll arrange a meeting to confirm how you’d like to set up LFPSE in your system.
We’ll complete the set up in your Staging system first before any changes are made to your Live system.
We recommend reading through the 8 configuration options below in preparation for the call.
Once we have confirmed your set up, we’ll be able to discuss timescales for testing and going live with LFPSE reporting.
1. Are any changes needed to your Locations to accommodate your ODS code(s)?
We’ll review your system Locations to:
- Confirm which Locations may need to submit LFPSE data. (Not all Locations in your Radar system need to be enabled to submit LFPSE data).
- Ensure your ODS Codes are compatible with your existing Location set up.
- If you have multiple ODS codes we’ll map your ODS codes to your system Locations.
- A Location in your system can only have 1 ODS code associated to it.
- The same ODS code can be associated to more than 1 Location.
- We can set an organiation ODS code if you only have 1 ODS code or to submit data for any Locations that don’t have their own ODS code.
2. Which events in your system will need to submit Incident data to LFPSE?
You may have existing incident reporting options in Radar that need to start submitting data to LFPSE e.g. Incident, Fall, Wound.
Alternatively, new LFPSE Incident event(s) can be set up.
Some organisations opt to create a separate LFPSE Incident event so that the standard incident reporting process remains unchanged for their teams when implementing LFPSE.
However, having a separate LFPSE Incident event increases likelihood of having to duplicate data entry across events.
3. Which events in your system will need to submit Good Care data to LFPSE
You may have existing events in Radar that need to start submitting good care data to LFPSE e.g. Compliments or Excellence Reporting.
Alternatively, a new LFPSE Good Care event can be set up if you don’t already capture this data in Radar.
4. Do you want to implement LFPSE Outcome and Risk reporting?
These are currently optional and are implemented upon request.
5. Do you want to integrate / merge the LFPSE reporting questions into your forms or keep them as separate forms?
| Option | Description | Advantages | Disadvantages |
| a) Keep your local event forms and the LFPSE forms separate. | Users would complete an LFPSE form and a local form when reporting an LFPSE event (e.g. when reporting an incident users would fill out the LFPSE form, then fill out your own local form). | This enables you to still edit your own forms, whilst the LFPSE form is locked. | This option cannot be used if you allow events to be reported externally via a webpage. You may have to remove questions from your local forms to avoid duplication of data on the LFPSE form. |
| b) Integrate the LFPSE reporting questions into your existing event forms. | Users would complete 1 form to submit an LFPSE event. | Users have less forms to fill in when reporting an event. | Your forms would be locked and any changes would need to be requested via our Support team. This option takes longer to configure. |
6. How do you want to integrate the LFPSE Governance questions into your event workflow?
| Option | Description | Advantages | Disadvantages |
| a) Add the ‘LFPSE Governance’ form as a new step in your workflow.
| Let us know where this should appear in your workflow via your workflow spreadsheet, the timescale for completing the form and who would fill it in. | This enables your own forms to be edited in the Form Editor, whilst the LFPSE form is locked. | You may have to remove questions from your local forms to avoid duplication of data on the LFPSE form. |
| b) Integrate the LFPSE governance questions into an existing workflow step. | Let us know what form to add these questions to and whether there are any existing questions that are duplicates of the LFPSE questions. E.g. Add LFPSE questions to the existing ‘Notifications and Communications’ form. | Users don’t need to complete a new form as part of the workflow. | Your own form would be locked and any changes to the form would need to be requested via our Support team.
|
7. Do you want the LFPSE submission description to be generated from the Radar Description/Title of the event OR the LFPSE question ‘Describe what happened’?
By default, submissions will use the information entered into the LFPSE question ‘Describe what happened.’
If you choose to use the Description of Event, we can hide the ‘Describe what happened’ question on the LFPSE form. This is the only question which may be hidden.
8. Is any customisation to the LFPSE questions needed ?
The following cannot be edited:
- The text / phrasing the of LFPSE questions
- The options available in the drop-down lists cannot be edited
- LFPSE questions cannot be hidden from users
- Mandatory questions must remain mandatory
The following customisation can be completed:
- Additional hint text or guidance can be added to the LFPSE questions
- A default option can be selected for drop down questions (however users will be able to edit this if desired)
- Additional dependencies can be added to display questions when desired
- Optional questions can be made mandatory
4. Test your LFPSE set up
Radar Testing
Once we have completed your LFPSE configuration in your Staging system, we’ll run some test submissions as required by NHS England.
These test submissions will show in your Radar Staging system only and do not appear in your LFPSE account.
We’ll confirm the date your LFPSE testing will be completed.
We recommend setting your LFPSE go live date 2 weeks after your test date, in case there are any issues that occur.
Your Testing
You can also complete any of your own testing in the Staging system. The tests you complete in Staging will not be submitted to LFPSE.
E.g.
Ask some users to report an incident and fill out the LFPSE form to get feedback on the process.
Check that you’re happy with any updates to your workflow.
Whilst testing the LFPSE configuration, you can also complete Steps 4 and 5.
5. Enable Your Locations for LFPSE reporting
Within your Live system you will need to update your Locations to:
- Enable LFPSE reporting for any Locations where patient-related events are reported. (Required)
- Add your ODS codes (Optional - only applicable if you’ve got multiple ODS codes)
- Configure Healthcare Benchmarking fields to pre-populate some LFPSE questions (Optional)
N.B. If Locations are not enabled for LFPSE reporting the LFPSE form will not be available for users to complete when reporting events.
To action the above:
- Go to Administration > Locations
- Click on a Location that needs to be able to report patient safety events and click ‘Edit’
- Add the Location ODS code (only applicate if you’ve got multiple ODS codes)
- A Location can only have 1 ODS code.
- You can add the same ODS code to more than 1 Location.
- Set ‘Is a PSIMS reporting location’ = YES
(PSIMS is the original name for LFPSE). - Set ‘Healthcare Benchmarking’ fields to pre-populate certain fields in the LFPSE forms and help your staff fill out the forms quicker (Optional)
| Healthcare Benchmarking Option | Related LFPSE Question |
| Primary location type | Where did the incident happen? |
| Primary service | Which service types were involved? |
| Primary speciality | Which speciality does the incident relate to? |
6. Prepare for Go Live
Before going live consider the following:
- How will you train your staff on completing the LFPSE form? (if applicable)
- Will your DPIA (Data Protection Impact Assessment) policy need updating to reflect data captured within LFPSE?
7. Get your API Key and Go Live!
NHS England’s LFPSE team can issue you with an API security key to connect your Radar Healthcare account with your LFPSE account. This allows LFPSE submissions to start coming through from Radar when you go live.
Please see the guide at the bottom of this article for instructions on how to get your API key.
N.B . You should request an Unlimited API key.
If you have more than one API key, add your Primary API Key in Radar
When you have your API key, enter this in your Live Radar Healthcare system:
- Go to Administration > PSIMS
- Click ‘Maintain PSIMS details’ and add paste your API key into the box
- Click Submit > Save
- If correct, your API status should be ‘Good’
Radar Healthcare will transfer your LFPSE configuration to your Live system once testing has been completed and LFPSE data can start being submitted!
Please check that your submissions are coming through by:
- Viewing submissions in Radar > Administration > PSIMS
- Logging into the LFPSE portal to check the submissions appear here
If there are any issues, please email support@radarhealthcare.com.