Skip to main content

Pharmapod Release Notes Sprint 64

Pharmapod Release Notes Sprint 64

Eogan McCullen avatar
Written by Eogan McCullen
Updated over 2 years ago

Bugs

Settings

1. Bug 892: Settings - Group of Facilities - Group Name sort doesn’t work

• Description: Within Settings, Groups of Facilities, and utilizing the “Group Name” header filter, names were not filtering alphabetically. This bug has been fixed as part of this release.

2. Bug 298: Settings > User System Activity > Analytics not picking up mobile sign up

• Description: Within Settings, User System Activity, when a user was added with the Notification type “Phone”, their number of logins did not update in the “User System Activity” table. This bug has been fixed as part of this release.

System Configuration

4. Bug 893: System Configuration - Action Points & Learning Points - Value Sort not working

• Description: Within System Configuration, Action Points, and Learning Points, the “Value” header was not filtering alphabetically. This bug has been fixed as part of this release.

5. Bug 894: System Configuration - Global Settings - Professional Position - sort

• Description: Within System Configuration, Global Settings, Professional Position, the “Name” header was not filtering alphabetically. This bug has been fixed as part of this release.

6. Bug 1042: System Config > Facility types: sorting by icon

• Description: Within System Configuration, Facility Types, the “Name” header was not filtering alphabetically. This bug has been fixed as part of this release.

7. Bug 6297: Collaborator Actions Usage Count is not updating when usage is deleted from event summary

• Description: Within System Configuration, Drop Downs, CQI Widget Options, and “Edit” for Collaborator Actions, the “Usage Count” was not updating when collaborators were being removed from events e.g. incidents. This bug has been fixed as part of this release.

8. Bug 6294: Not able to delete the Inactive Action in System Configuration Module

• Description: Within System Configuration, CQI Widget Options, Actions, Edit, it was not possible to delete an action marked as inactive (the trash can icon was greyed out). Now, you can delete an inactive action which has never been used/selected, but if an action has a usage count of more than one, it cannot be deleted as deleting would alter the actions analytics.

Insights Pro/Lite

9. Bug 1628: Insights Lite/Pro Root Cause not showing Pharmapod Average

10. Bug 2285: Insights Pro > Event Trend > Number of events by facility Chart freezing with specific filters

• Description: Within Insights Pro, Event Trend Analysis, Number of Events by chart and applying different combinations of filters the charts stayed loading in certain scenarios. This bug has been fixed as part of this release.

11. Bug 6427: Insights Lite & Pro > Charts > Pop-up from clicking color code on Pharmacy list, is showing No results

• Description: Within Insights Pro, Charts, (all chart types), when clicking on the colour code on the pharmacy list, no results are visible. This bug has been fixed as part of this release.

12. Bug 6766: Where do Errors Typically Occur chart not adding up to 100 %

• Description: Within Insights Pro, Root Cause, the values in the “Where do Errors typically occur” table were not adding to 100%. This bug has been fixed as part of this release.

13. Bug 6943: Insights Pro > Amchart Based Report 'Since Beginning' pulling incorrect start date

• Description: Within Insights Pro, using the Date filter for all reports, and selecting “Since Beginning”, the incorrect date was being applied. This bug has been fixed as part of this release.

14. Bug 7029: Insights Pro > Charts > Displaying Hazard and Accident counts

• Description: Within Insights Pro, Charts, some hazards and accidents were pulling into the tables. This bug has been fixed as part of this release.

This only applies to customers who use the “Health and Safety” module. If you do not have the “Health and Safety” module you can ignore this section.

15. Bug 6149: Insights pro & lite- Charts- label fix as all event types showing in incidents per week & month charts

• Description: Within Insights Pro, Charts, the “Incidents per day of the week, and day of the month” charts have been renamed to “Events per day of the week, and month”.

SOP’s/Procedures

16. Bug 1635: My SOPs shortcut not working

• Description: Within SOP’s, SOP Analytics/SOP Management, when clicking on the “MY SOP’s” shortcut the page wasn’t reverting to the “MY SOP’s” dashboard. This bug has been fixed as part of this release.

17. Bug 6085: SOP File name is not displayed in the SOP Download popup from Incident Summary Page

• Description: Within the event summary page for a particular case (e.g. incident) and clicking on the SOP Download button, in the SOP’s section, the SOP file name wasn’t visible. This bug has been fixed as part of this release.

Patient Safety Report (Not PQS)

18. Bug 7028: Safety Report > Form Type filter & status filter is not applied to the event counts in downloaded file

• Description: Within Incidents/Medication Safety Events, Safety Report, and searching for events, the event count and status within the system did not correspond with the figures in the downloaded report (word document). This bug has been fixed as part of this release

19. Bug 2409: Safety Report showing month not in filter

• Description: Within Incidents/Medication Safety Events, Safety Report, and applying date filters, not all of the months selected in the date filter were showing in the resulting safety report (word document). This bug has been fixed as part of this release

Assessments (PSSA Canada, PASS Pro Ireland)

20. Bug 7048: PAS Lite> unable to complete assessment with section 6 marks as N/A (Ireland Only)

• Description: Within Pharmacy Assessment System Lite, when Section 6 was marked as N/A the user was unable to complete the assessment in its entirety. This bug has now been fixed as part of this release. When Section 6 is marked as N/A by the user, the assessment can be completed provided the other 5 sections are marked as completed.

21. Bug 7190: Assessment Facility Sync - Names Not Updated in Head Office View

• Description: Within Assessments, Head Office view, when a facility name was updated the old facility name was visible. This bug has now been fixed as part of this release. The current name of the facility will show within Assessments, and Head Office view.

Enhancements

Assessments (PSSA Canada, PASS Pro Ireland)

22. User Story 6966: Assessments: Prepopulate the action owner name under SMART Actions

• Description: Within Assessments, when a new Action is created, the original action owner’s name should show within the “SMART Action Plans” section. The Action owner can be amended by clicking on the action, the “Owner” dropdown, and selecting a different user.

23. User Story 6992: Assessments: Write a functionality which enables the system to display users assigned to the facility

• Description: Within Assessments, SMART Action Plans, and adding a new action, the “Owner” dropdown list should show a list of all active users setup within the account assigned to the relevant facility who is completing the assessment.

24. User Story 7077: Pharmapod PSSA Update the Likert Scaling System with new wordings

• Description: Within Assessments, the below new metric options for all the domains are visible at the top of each section:

25. User Story 6940: Assessments: Functionality to apply different labels for likert scale questions

• Description: The safety score is calculated based on the answers provided by the user for each question. The average score is calculated using all domain question answers excluded question where Not Applicable was selected. The full assessment safety score is taken as the average of all domain safety scores and is only calculated by the following metrics:

26. User Story 6873: Assessments > Apply Demographics to the new AIMS PSSA v2.2022-08

• Description: When a user creates a new Assessments submission, the new Demographics questionnaire will open. If the users have already filled out prior assessments, the system should pre-populate the details which were provided previously.

Enhancements

Cases

27. User Story 6904: Cases > All Closed > Date Selection Changed to "Date Closed"

Description: Update Cases > All Closed > Date Selector (data that is displayed)

FROM "Event Date" (events.event_date)

TO "Date Closed" (events.date_closed)

Hover Helper Updated to: "Year-Month an event is closed (excludes misrecorded events)"

Display the Date after selected as "YYYY-MM" based on selection (currently displays MM-YYYY)



Update the Displayed Columns as follows:

  • REMOVE the following columns:

    • Age (in days)

    • Actions

  • ADD the following after "Status"

    • Date Closed: YYYY-MM-DD (should display the correct date based on the facility the event was closed)

    • Days to Close = date_closed - date_created (ignoring time)

    • Closed By: <User's Fullname Who Closed the Event based on events.closed_by>

  • CHANGE Assigned Team and Assigned User Column to 1 Column called "Assigned Team/User"

    • When both a Team & User are assigned it will displays as "Team Name (User's Fullname)"

    • When only a Team is assigned is will just display "Team Name"

    • When only a User is assigned is will just display "User's Fullname"

28. User Story 6905: Cases > Table Update - Change 'Age (in days)' to "Days Open"

• Description: The "Age (in days)" header within Cases, CM Queue has been renamed to to "Days Open" (= Today's Date – Date Submitted).

29. User Story 6906: Cases > Misrecorded > Display Misrecorded Date, Misrecorded By, Reason

Description: Update Cases > Misrecorded Events

Update the Displayed Columns as follows:

  • REMOVE the following columns:

    • Age (in days)

    • Actions

    • Assigned Team

    • Assigned User

  • ADD the following after "Status"

    • Date Misrecorded: YYYY-MM-DD (should display the correct date based on the facility the event was submitted from -- events.date_misfiled)

    • Misrecorded By: <User's Fullname Who Closed the Event based on events.misfiled_by>

    • Misrecord Reason: Value for events.event_misfiled_type_id

Order Table by: Date Misrecorded (Desc order - ie: Newest to Oldest)

Did this answer your question?