Pharmapod Release Notes Sprint 83

1. User Story 13270: Update Text for NHS Data Sharing Section (England Only)

• Description: At the end of the LFPSE Incident and Good Care forms, the following text has been updated for the “NHS Data Sharing” section to the following:

• NHS will share this record with other organisations, including the relevant ICB. NHS will not share your personal data outside of your organisation. We will process your personal data only for the purpose set out in the Terms of Use.
​
​

• To opt out of record sharing, check the box below:

•

• [checkbox] I do not want to share this record with the organisation that provided the care.

•

• Users should only select this option if they have a specific need to do so. NHS England may share this record with other relevant organisations under specific data sharing agreements (as set out in our Terms of Use). We make every effort to remove any unwanted personal identifiable data provided by you as part of this record before the data is shared with any other organisation.

•

2. User Story 13336: Medication Incident & Good Catch [Global] Updates - What happened, Incident Details, Disclaimer for what Happened question [Sprint 83]

• Description: Within the Incident and LFPSE Incident forms, the following updates have been made:

Update this category 'Clinical/drug utilization review (DUR)/contraindications (e.g. duplicate therapy)' to 'Incorrect clinical assessment (missed DUR, drug interaction, duplicate therapy)' under "Clinical and Other"

Add below new sub-categories to the updated category

Incorrect assessment (pharmacist prescribing)

Incorrect indication (pharmacist prescribing)

Treatment ineffective (pharmacist prescribing)

Adding two new categories called "Pregnancy" and "Chemical restraint used (e.g. antipsychotic)" under Incident Details - Situations with Risks

Update the disclaimer for the question 'Describe the facts of what happened'

"***In order to protect confidentiality, please do not identify the people by name, and please do not include any personally identifying information (e.g. patient/resident name, names of staff or management/owners, address or name of premises) when describing the details of the event, as this free text field cannot be anonymized*** You may use initials. Please give a factual, chronological description of the sequence of events. Do not pass judgment or provide explanations. Do not speculate on the potential for harm, or the possibility of a link between potential harm and the medication error avoided. State facts as they were known at the time the event was discovered that you consider important or that could help to learn from what happened."

3. User Story 13337: Increase the characters counts for Actions and RCA tool

Description: Under the summary page (for all events) >> Actions Widget >> Increase the characters limit from 250 to 3000 for the SMART Action Plan field.

Under the summary page (for all events) >> Root Cause Widget >> Increase the characters limit from 250 to 1000 for the Root Cause Identified field

4. User Story 13258: Insights Pro - Add a filter 'Form Type' to event trend analysis page and all other filters in different tabs

Description: Within Insights Pro, Event Trend Analysis, a new filter is added called “Form Type”. All assigned forms will show in this filter and can be selected when running a report within “Event Trend Analysis”.

5. User Story 13267: Add Hover Helper with Tooltip

Description: Within the “Good Care” form, hover over/helper text has been added to the “Describe what happened section” as follows:

Include details of anything you think was important, or might help us learn from what happened. Avoid including any identifiable information such as names of staff or patients here. The national patient safety team focus their primary learning activities on the information provided here, so a full description and sequence of events will contribute to better learning and improvement.

6. User Story 13269: Add new mandatory date field

• Description: Within the Good Care form, a new mandatory date field is added. This field works like 'Date and time error occurred', except the time will not be collected and question label is as required by LFPSE. It should be considered as event date of the good care.

7. Bug 12918: LFPSE Integrations > Add ability to send request to LFPSE to delete the misrecorded events

• Description: If an event has been closed/reopened and misrecorded It would have sent to the NHS as part of the LFPSE integration upon closure. Now, a new function is built within the Integrations module, whereby pharmacies can send delete requests to the NHS for LFPSE entries which have previously sent but are now misrecorded. Within Integrations, a new button is added called “Send Delete Requests”. When selecting the relevant event ID’s on the left-hand side and the “Send Delete Requests” button, these requests then send to the NHS.