Hospital Network Connectivity

Have more questions? Submit a request

Below is a general diagram for network communication between SafeNSound and the Hospital Network.

hops connect.png

  1. An ADT interface for processing patient details and orders then matching them to the devices in the SafeNSound application.
  2. The second interface is a connection to the onsite Spacelabs XprezzNet server. This server allows SafeNSound to push and pull data from the monitors and automates much of the workflow management and alarm reporting. This server (can be virtual) is required for automation of the system.
  3. The third interface is a connection between the SafeNSound application servers and your local Active Directory servers. This allows all authentication to pass directly to your own internal systems. The SafeNSound system does NOT store any passwords.
  4. The forth and less common is a connection to your staffing services. This allows the SafeNSound system to auto sync all staffing changes.

Why do we need a Site-to-Site connection?

The site-to-site connection is used to connect the Spacelabs Cloud and to the local Spacelabs system. This connection allows our systems to securely process the encrypted data and report on that data through our interface.

Monitoring and Redundancy 

The site-to-site connection is monitored 24/7 with auto escalation on alerts if connectivity fails. 

 

Spacelabs Cloud Endpoints

USA Firewalls

IP: 52.6.70.250
IP: 52.73.18.190

 

IPSec VPN Tunnel

Local ID: 52.6.70.250

 

URL's 

Replace {account#} with your system account number provided by Spacelabs Cloud Services team.

https://{account#}.safensound.io

https://export-download.{account#}.safensound.io

https://bridge.{account#}.safensound.io

https://api-1.{account#}.safensound.io

https://api-2.{account#}.safensound.io

https://api-3.{account#}.safensound.io

https://api-4.{account#}.safensound.io

https://api-5.{account#}.safensound.io

https://api-6.{account#}.safensound.io

https://waveform-proxy.{account#}.safensound.io

https://waveform-proxy-1.{account#}.safensound.io

https://waveform-proxy-2.{account#}.safensound.io

https://waveform-proxy-3.{account#}.safensound.io

https://waveform-proxy-4.{account#}.safensound.io

https://waveform-proxy-5.{account#}.safensound.io

https://waveform-proxy-6.{account#}.safensound.io

https://waveform.{account#}.safensound.io

https://waveform-1.{account#}.safensound.io

https://waveform-2.{account#}.safensound.io

https://waveform-3.{account#}.safensound.io

https://waveform-4.{account#}.safensound.io

https://waveform-5.{account#}.safensound.io

https://waveform-6.{account#}.safensound.io

 

 

 

Articles in this section

Was this article helpful?
0 out of 0 found this helpful