Email is used for product update announcements, password resets, initial user invitations, and interactions with the Pulsara support team.
Permit all incoming email from *@*.pulsara.com in your email system. Prevent email from *@*.pulsara.com from being tagged as spam. Because Pulsara relies on a third party for email services, if you filter incoming emails by IP address, please ensure your systems are looking up our SPF record to obtain a list of IP addresses from which we send mail.
Pulsara systems utilize dynamic load balancing to automatically distribute incoming application traffic across a web server cluster. Additionally, to support System Continuity best-practices, our systems leverage multiple geographically separated data centers.
Please permit traffic originating on your network to the destination hosts and specified ports in the tables below.
Pulsara
| Destination Host | Ports | Description |
| *.pulsara.com | TCP/443 |
For API traffic from Pulsara iOS and Android Clients. For the Pulsara browser app screens, assets, and API traffic. |
Audio-Video Conferencing
If “Video Calling” has been enabled for your account, your Pulsara users can participate in secure Voice or Voice + Video conference calls.
Zoom
Pulsara uses the Zoom platform for synchronous voice, video, and conferencing capabilities.
| Destination Host | Ports | Description |
| *.zoom.us |
TCP/80 |
For voice and video communications. |
| *.zoom.us | UDP/3478 UDP/3479 UDP/8801-8810 |
To provide the highest quality voice and video communication capabilities. UDP is highly recommended for better quality audio and video. The protocol favors timeless over reliability which is consistent with human perception. |
After configuring your firewall, preliminary Zoom testing can be conducted using the instructions here.
If you are able to participate in the Zoom test conference, Pulsara App users on the same network should also be able to participate in Zoom-based conferences.
Specific network and firewall settings for Zoom are available here.
Click Here to View Additional Zoom Security Information.
Native Mobile Device Capabilities
Mobile App Downloads and Updates
Pulsara’s mobile apps and mobile app upgrades are distributed through the Apple App Store and the Google Play Store.
Either:
Push Notifications
Pulsara uses Push Notifications for its delivery of alerts. iOS devices use Apple Push Notification Service (APNS) for this purpose. Android devices use Google Firebase Cloud Message for the delivery of push notifications.
After configuring your firewall(s), we recommend sending and testing push notifications on devices of both types connected to your organization’s network(s) to which devices will be connected. This can be accomplished through the Pulsara mobile apps.
Apple Push Notifications Service (APNS)
| Destination Host | Ports | Description |
| 17.0.0.0/8 | TCP/5223 | Used by iOS devices to receive push notifications from APNS. The APNS servers use load balancing, so your devices won't always connect to the same public IP address for notifications. It's best to allow access to these ports on the entire 17.0.0.0/8 address block, which is assigned to Apple. |
For additional information, see IP addresses for default domains.
| Table 1: Google FCM for Push Notifications | ||
| Destination Host | Ports | Description |
|
Per Google's Guidelines:
|
TCP/443 |
Used by Android devices to receive push notifications via Firebase Cloud Messaging. Per Google's guidelines: If your network implements Network Address Translation (NAT) or Stateful Packet Inspection (SPI), implement a 30 minute or larger timeout for our connections over ports 5228-5230. This enables reliable connectivity while reducing the battery consumption of your users' mobile devices. |
Mobile App Analytics, Crash Detection, and Problem Resolution
Pulsara’s mobile apps have the capability of reporting crashes, other errors, and analytics. Pulsara uses these reports to proactively correct issues or problems as quickly as possible (sometimes even before impacting customers) and to improve app usability. We use Google Firebase for this purpose.
ePHI is never transmitted to Google Firebase.
Pulsara clients will function properly even when devices are unable to access Google Firebase for the purpose of sending analytics and crash data.
Google does not publish domains or firewall-whitelist guidance for Firebase Crashlytics or Firebase Analytics. As such, Table 2 (below) is provided strictly for informational purposes.
| Table 2: Google Firebase for Analytics and Crash Reporting | ||
| Destination Host | Ports | Description |
|
cm.googleapis.com |
TCP/443 | Used for analytics, crash detection, problem resolution. |
Ensure your organization’s personnel are using browsers and/or devices supported by Pulsara and listed here.
If Wi-Fi is to be used for internet connectivity, determine which Wi-Fi network name (a.k.a. “SSID”) will be used with staff mobile devices, and obtain Wi-Fi passwords or have your IT department configure this for you.
Wi-Fi must have a persistently active connection, must not require staff members to repeatedly log back onto the system, and must have excellent coverage throughout the facilities.
Prior to testing, a comprehensive connectivity Audit should be completed to identify any WiFi or Cellular connectivity issues:
Please consider the following:
It is our recommendation, as best practice for system continuity, that devices used by mission critical functions, such as ED nursing stations, have a cellular data plan as a backup method of connecting to the Internet.
If your facility will use hospital-provided iOS device(s) for Pulsara outside of an MDM, then identify the Apple ID that will be used on the device(s) for the installation of the Pulsara application. This Apple ID may be required to authenticate with the Apple App Store for future upgrades of the Pulsara app.
See this MDM Checklist for more information.
None. When a mobile user needs to access data, it is retrieved from the Pulsara platform. Data is only present in volatile memory on the device.
Pulsara does not provide hardware. Please work with your Pulsara regional team to determine the appropriate devices for use at your organization.
A list of supported devices is available here.
Consistent with Healthcare IT best practices, please work with your Pulsara regional team and your facility to determine how accounts are provisioned.
For information regarding Pulsara system status, please visit our status page here.
This page displays the status of the Pulsara platform. You can also sign up for status notifications by clicking on "Subscribe to Updates”.
Pulsara releases updates to its mobile applications frequently. To optimize your experience with the Pulsara platform, it is highly recommended that you enable auto-updates on your devices.
Pulsara fully tests each release for regressions against all supported devices with the use of manual and automated testing sequences. In advance of an update, release notes will be provided with timeline, scope, and details of the release.
The Pulsara applications are intended to facilitate communication for and accelerate preparation of acute care coordination. The applications are not intended to be relied upon for making diagnostic or treatment decisions or used in connection with monitoring a patient.
