July Product Update

Update Summary: 

• Face ID Login for iOS
• Configurable Critical Alert Volume for iOS
• Incident Patient by Destination View Enhancements
• Incident Archiving
• Add Transport Button in Pulsara Web
• New Location for Certain User Invitations
• iOS Mobile Support Announcement

Face ID Login for iOS

What's changing

• Users now have the option to log in and/or PIN in with Face ID for Pulsara on iOS.
• Fingerprint ID can be used in place of Face ID on older devices that do not support Face ID.
• If the feature is not used, manual input of username and password or PIN can still be used to access the application.
• This feature is not supported on devices running Pulsara that are used by multiple people.

Login screen for a device configured for Face ID - PIN screen for a device configured for Face ID

Who’s impacted

• All Pulsara iOS users who enable the feature using a device that supports Face ID or Fingerprint ID

Why you’d use it

• Log in to Pulsara without having to manually type your username and password
• PIN in to Pulsara without having to input your Pulsara PIN
• Faster and easier access to Pulsara

Rollout Timing

• The feature will be available in Pulsara mobile version 50, scheduled to begin release on July 10th

Getting started

• Admins: 
  • No action required
• End Users: 
  • Upgrade to Pulsara mobile version 50 and enable the feature in Pulsara Settings
    • The phone running Pulsara must have the Face ID feature enabled under Settings
    • Enable the Face ID login and/or PIN options in Pulsara Settings

Learn more about using Face ID

Configurable Critical Alert Volume for iOS

What's changing

• Critical Alerts allow iOS users to receive audible alerts for new patient channels even when the device is in Do Not Disturb or has the physical mute button enabled.
• In Pulsara iOS version 50, users will be able to change the volume of critical alerts.
• The default value is 14, but can be customized to a volume on a scale from 2 - 20.
• Critical alert volume will not change automatically for Pulsara iOS users who upgrade from a previous version.

            Critical Alert Volume Setting                                Critical Alert Volume Slider

.     

Who’s impacted

• All Pulsara iOS users who have critical alerts enabled

Why you’d use it

• Tailor critical alert volume to a level that is most appropriate for your Pulsara usage
• Ensure volume is loud enough for busy situations like the ED
• Turn volume down for quieter places like patient bedside 

Rollout Timing

• The feature will become available in Pulsara mobile version 50, scheduled to release on July 10th

Getting started

• Admins: 
  • No action required
• End Users: 
  • Upgrade to Pulsara mobile version 50 and enable the feature in Pulsara Settings
    • This setting is available only if critical alerts are enabled for Pulsara

Learn more about Configurable Critical Alert Volume

Incident Patient by Destination View Improvements

What's changing

• We added a new full-screen pop-out mode called Command View to increase the screen area available to view summary information.
• The summary now automatically refreshes every 15 seconds, so the Refresh button was removed. 
• The Totals row now appears at the top where it is always visible, regardless of how many facilities are in the list and the current scroll position.
• The facility name column is now wider, making it easier to see where patients are headed or currently located.

Who’s impacted

• Pulsara web users who use the incident summary view to see patient transport status and location

Rollout Timing

• These improvements were released on June 25th

Incident Archiving

What's changing

• We added the ability to archive incidents. 
• The Archived status is meant to be used for an incident that is stopped, no longer needs changes, and no longer needs to appear in the list with active incidents.
• Archived incidents are filtered out of the incident list by default, but can be viewed by selecting the  “Archived” filter.
• An Archived incident can be restored and moved back to Stopped status.