Pharmapod Release Notes Sprint 63

1. Bug 6753: Record Event Buttons - Icons have same look/feel on Laptop/Tablet/Phone Screen Size

• Description: The formatting of the event buttons when logged in on a laptop/PC was different compared to a phone/tablet (smaller screen). Now the formats are aligned, and these buttons look the same regardless of device. This applies to all event form buttons e.g. incident and near miss.

2. Bug 6756: Event Trend Analysis > Events over Time (ALL) > CSV Exports - Breaks for Selection for any period that is 1 month or less

• Description: Within Insights Pro, Event Trend Analysis and running a report for the “Number of Events over Selected Timeline by Event Type” for less than one month, the file does not export to excel. This bug has been fixed as part of this release.

3. Bug 6531: Insights pro > Charts > Table displaying Navigation buttons for "No Results" in popup

• Description: Within Insights Pro, Charts, and in the table view, when selecting a numeric value for one of the options in the table view, a pop up-showing “No Results” would show. This bug has been fixed as part of this release.

4. Bug 6551: Charts > List of Events not showing events when selecting inactive facilities

• Description: Within Insights Lite/Pro and selecting an inactive facility in the “Selected Facilities” list, these events were not populating in the chart view. They were also not visible when clicking on one of the segments on the chart which shows the event details. This bug has been fixed as part of this release.

5. Bug 6141: Insights Pro GRLS > Event Trend Analysis - Event count is not matching with Export Data for This Month & Last Month search

• Description: Within Insights Pro, Event Trend Analysis, and the “Number of Events over Selected Time Interval by” charts, the figures in the charts should match the results for the identical filters applied in Export Data. This would be the case apart from misrecorded events which populate into export data. This bug has been fixed as part of this release.

6. Bug 6144: Event Trend Analysis > Number of Events by Organisation - Result not populated in the chart

• Description: Within Insights Pro, the Event Trend Analysis, and “Number of Events by Organization”, after applying filters and selecting “Generate Report”, results were not populating into the chart. This bug has been fixed as part of this release.

7. Bug 6554: Getting 500 Error while using "Normalize by Prescription count " option in Insights pro > Event Trend Analysis

• Description: Within Insights Pro, the Event Trend Analysis, and “Number of Events by Organization”, and selecting the “Normalize by Prescription Count filter, an error 500 message would appear after selecting “Generate Report”. This bug has been fixed as part of this release.

8. Bug 6549: Insights Pro > Medication > Shelving Analysis > Active Ingredients

• Description: Within Insights Pro, Medication, Shelving Analysis, and Active Ingredients, when the chart is toggled to display this information- then the chart will alphabetically sort the "Active" ingredient of a drug and display events refined by the desired date search parameters.

9. Bug 6802: IM > Safety Report > Search Results Table - Status of events closed after Closure Requested, still displays with status "Open (Closure Requested)"

• Description: When attempting to generate a patient safety report, and searching for events, in the case whereby an event was closure requested and subsequently closed, the status of the event shows as “Open (Closure Requested) in the search results. This bug has been fixed as part of this release.

10. Bug 6548: IM > Safety Report > count of contributory factors & category for WHAT happened is incorrect in the downloaded file

• Description: When executing a safety report, mis recorded entries were populating into the search results and the subsequently downloaded word document. This bug has been fixed as part of this release.

11. Bug 6819: IM > Safety Report > When user selects combination of 2 months, system displays only the starting month data

• Description: When attempting to generate a patient safety report, when a user selects a combination of two months, the subsequently downloaded word document only displays the starting month’s data. This bug has been fixed as part of this release, now both months selected display within the generated word document.

12. Bug 6559: IM > Safety Report > Event count in the download is not matching with the search result when selected Status is not "All"

• Description: When attempting to generate a patient safety report, and selecting a particular form type e.g. incident, the event count in the downloaded report was not always matching the search results prior to generating the report. This bug has been fixed as part of this release.

13. Bug 6937: Daily notification email's subject is wrong

• Description: The Daily Summary Email template should have the following subject template:

"Pharmapod daily summary of activities - DDth MON YYYY".

14. Bug 6818: Assessment > Actions Card > Wrong 'Assessment' Name

• Description: Within Assessments, Actions, the name within the Action Cards for outstanding actions differed from the names of the assessment submissions they were assigned to. This bug has now been fixed as part of this release.

15. User Story 6695: Completed Dashboard: Toggle to hide abandoned assessments

Description: Within Assessments, Completed Dashboard a toggle has been added to exclude abandoned assessments from the dashboard view.

16. User Story 6892: Head Office View: Maintaining the consistency of Assessment name based on the filter selected

Description: Within Assessments, Head Office View, the system should show the short form of the assessment name under each facility in the Head Office View based on the filter chosen by the user.

17. User Story 6715: Assessments Facility Data Sync

• Description: Facility Metadata displayed in for Assessments will be updated when it is updated in Settings > Facilities. For example, if your Facility name is changed from "Pharmacy #21" to "RxPharmacy #21" this change will reflect in Assessments the following day. The Facility Accreditation Number has also been pulled into the Assessment data set along with the Regulating Body.

18. User Story 6702: Head Office View: Adding a information button to safety score

• Description: Within Assessments, Head Office View, when hovering over the information button, the system should provide the following prompt "The assessment's safety score is calculated based on the average safety score of all sections/domains."

19. Task 6088: PQS Admin access, view reports in Insights by facility and not for the entire org

• Description: The PQS “Admin” access toggle within “Modules Access” has been removed. Now, the PQS User access remains in isolation and when assigned to a user, users can access the PQS reporting tool. Users can also access previous submissions for the facilities they are assigned to within Insights, and Safety Reports. In the case whereby a user is assigned “Case Manager” access they can view all submissions for all facilities (similarly to Cases).

20. User Story 6600: Cases & Search > Expand to include events for a User's Inactive Facilities

• Description: Within Cases, and search, results for inactive facilities (which a user previous had access to) will pull into the various subsections e.g. CM Queue, All Closed etc.

21. User Story 6717: System Configuration - Form Setup - Auto Close

• Description: Within System Configuration, Global Settings, and Forms Setup, a new option has been added called “Auto Close Events”. This option can be selected for all forms and gives users the option for forms to be automatically closed immediately (On initial submission excludes drafts), and after a certain period of time once they are created (After a specified number of days) e.g. 30 days. The auto-close feature does not include drafted events, these events would move to Closure requested as they are incomplete. When “Never” is selected the auto-close feature is not implemented for the specific form. Events are flagged to say if they are auto-closed within different portions of the system e.g. Cases, and the event summary page.

22. User Story 6909: Safety Report - Question 2 & 3 updated to Homes and Pharmacies and aligned name to "Safety Report"

• Description:

1) Update Question 2:

FROM "What patient safety improvements have occurred in the pharmacy because of the actions the team has taken over this reporting period?"

TO "What patient safety improvements have occurred because of the actions the team has taken over this reporting period?"
​
(2) Update Question 3:
FROM "What has the team done in response to any relevant national patient safety alerts and drug recalls over this reporting period?"

TO "What has the team done in response to any relevant patient safety alerts and/or drug recalls over this reporting period?"
​
(3) Change the module name to "Safety Report"

(4) Remove the word "Patient" from "Patient Safety Report #967" in the PDF upper right header, so it would display "Safety Report #967"

(5) Change the pre-populated report name to be "Safety Report - YYYY-MM-DD" where the YYYY-MM-DD represents the day the report is ran. The user can continue to edit this as they want though.