Skip to content
  • There are no suggestions because the search field is empty.

August Product Update

Update Summary: 

 

Warn When Setting Trauma Level

 

What's changing

  • A new warning has been added when Trauma Level is changed in a patient channel. 
  • This change was implemented based on feedback that team members were changing Trauma Level without understanding this action often led to alerting Trauma teams. 
  • Now when Trauma Level is changed, Pulsara shows a message making it clear that the action may alert additional teams at your facility.

 

                      Select Trauma Level                              Warning When selecting Trauma Level


         Mobile_Trauma_Level_Selection_Edit           Warn_Setting_Trauma_Level_Mobile_Edit2

NOTE: This improvement was previously released for Pulsara Web and will become available in Pulsara Mobile in version 62 slated for release in mid-August.   

 

Who’s impacted

  • Team members who care for Trauma patients in Pulsara
  • People who may be alerted when Trauma Level is changed in Pulsara

Rollout Timing

  • This change was previously released in Pulsara Web
  • This change will become available in Pulsara mobile version 62 starting on August 13th

 

Incident Type, Parent Incidents, Streamlined UI

What's changing

  • A set of updates to the Incident Management functionality will be released, introducing substantial enhancements across three main areas.
  • Incident Type:
    • Specify Incident Type when creating an incident.
    • Combines with parent incidents (see below) to have a "type" and "sub type"
    • Feature supports future product incident reporting

select incident type

 

  • Parent Incidents:
    • In this version, the ability to nest related incidents under a parent incident is introduced. These nested incidents, called “Missions,” inherit the same owner as the parent incident.
    • Example uses for this feature:
      • Disaster management for an event like a hurricane, including missions for: evacuation, rehoming, 911 augmentation, special needs, etc.
      • A very large MCI spanning a large physical area. For example, a large bridge collapse with missions for: North side of bridge, South side of bridge, and under bridge (each a separate mission with its own location under one parent)
    • Missions tab
      • Create multiple child incidents or “Missions” under a single parent incident
      • List and a map view of all missions in the parent incident
    • Overview tab and Command views roll up patient counts by: Total across all Missions, per Mission, and per Destination
  • Streamlined User Experience and updated Screen Layout:
    • Streamlined Incident List screen with clearer information display
    • Easier and more discoverable information via tab navigation within an incident 
      • Parent incidents have tabs for Missions, Entities, and Overview Information
      • Missions have tabs for Patients, Entities, Overview
      • Create patients and/or upload a roster via the Patients tab
      • Add entities to an incident, and manage their permissions via the Entities tab. Promotes the concept of a regional team working on an incident "up a level" in the UI hierarchy.
    • The Overview tab consolidates incident details, location, and summary/destinations. Can still pop out a dedicated Command view.

 

Specify whether an incident is a parent

new parent incident

 

The Missions tab shows a list of Missions within a parent incident. The view includes a high fidelity map showing the location of all Missions.

 

missions in a parent

 

The Entities tab shows all entities participating in an Incident including the permissions they have for the incident. Add entities or transfer ownership from this view.

 

incident entities tab

 

The Parent Overview tab shows Details, Location and Summary info including the grand total of patients across all missions and separates out patient counts by Destination and Missions.

parent incident summary by missions

Missions have the Patients tab which lists all patients in the incident. This is also where new patients can be added via Roster Upload or the Create Patient button.


incident patient list

Who’s impacted

  • Incident Owners who have the need to group multiple related incidents together

Rollout Timing

  • These changes will become available in Pulsara Web starting August 12th
    • There are no Pulsara Mobile changes related to this feature

For more information on these changes, please see this knowledge base article.

 

Incident Patient Export (Beta)

What's changing

  • The ability to export a list of patients that are in an incident was added
  • Each row in the export displays information about a patient. Items displayed include Incident information, Patient Demographics, Condition, Chief Complaint, Transport status and more
  • If exporting from a parent, all patients in all Missions are included
  • The export button is available to administrators at the organization that owns the incident

Incident_Patient_Export

 

Who’s impacted

  • Incident Owners who have the need to export a list of people in an Incident into a .csv format

Rollout Timing

  • These changes will become available to beta testers starting August 12th

Request to join Beta by submitting a support ticket.

 

Coming Soon - Stryker Lifepak ECG Integration

What's changing

  • An integration is being added to allow digital ECGs from Stryker LIFEPAK 15 or 35 devices to be pulled directly into a patient channel in Pulsara Mobile.
  • This integration allows for attaching a digital image to the patient channel instead of taking a picture of the ECG printed from the device
    • When this integration is in use, ECGs can be attached to patient channels either directly from the cloud or manually using a picture of the printed ECG

Who’s impacted

  • EMS when their agency has the integration enabled for Stryker

Rollout Timing

  • These changes are in beta testing and will be released in the next couple of months