Appearance
System requirements
The CareSuite Server is a Linux-based system that can be installed on a physical or virtual machine. All software components are managed by the CareSuite itself. No manual configuration of the system is requried.
It can be installed on Ubuntu (preferred) and RedHat Enterprise Linux (RHEL).
Ubuntu (preferred)
| Topic | Requirement | Notes |
|---|---|---|
| Supported Versions | 24.04 LTS | Desktop or Server Edition |
| Graphical User Interface | Recommended | See notes below |
| RAM | 8 GB | |
| Disk Space | at least 80 GB | |
| Local root privileges | root/sudo permissions are requried | |
| Internet access | Partially required | See internet access |
RedHat Enterprise Linux (RHEL)
Click to show details for RHEL. Note that Ubuntu is the preferred installation method.
| Topic | Requirement | Notes |
|---|---|---|
| Supported Versions | 8 or 9 | Desktop or Server Edition |
| Graphical User Interface | Recommended | See notes below |
| RAM | 8 GB | |
| Disk Space | at least 80 GB | |
| Local root privileges | root/sudo permissions are requried | |
| Internet access | Partially required | See internet access |
Firewall/Ports
Inbound
The CareSuite Server uses the following ports which need to be open for incoming traffic:
| Port | Protocol | Required | Description |
|---|---|---|---|
| 80 | TCP | Required | Web Interface |
| 443 | TCP | Optional | Web Interface (SSL) |
| 8080 | TCP | Required | Receiving data from the Gets TCP Logger |
| 8081-8089 | TCP | Optional | Additional Gets TCP Loggers If multiple systems are managed, one additional port per system |
Outbound
The CareSuite Server connects to the following devices. Outgoing traffic has to be allowed for:
| Port | Device | Protocol | Required | Required for |
|---|---|---|---|---|
| 80 | GEC Configurator | TCP | Required | Configuring the Gets Nurse Call System |
| 80 | GEC Radio Hubs | TCP | Required | Monitoring of the Gets Radio System |
Internet Access
Internet access is required during the installation of the CareSuite.
To keep the system up-to-date, we recommend allowing internet traffic to at least the following hostnames permanently:
For Ubuntu based systems
The following hostnames are required if you do not use a custom local repository mirror:
| Hostname | Protocol | Description |
|---|---|---|
ch.archive.ubuntu.com | HTTP(S) (Port 80 and 443) | Ubuntu OS Updates |
security.ubuntu.com | HTTP(S) (Port 80 and 443) | Ubuntu OS Updates |
For RHEL based systems
Click to show details for RHEL. Note that Ubuntu is the preferred installation method.
The following hostnames are required if you do not use a custom local RHEL mirror:
| Hostname | Protocol | Description |
|---|---|---|
| cdn.redhat.com | HTTP(S) (Port 80 and 443) | RHEL OS Updates |
CareSuite
Dynamic IP addresses
The IP addresses of these hostnames might change. If you can, allow access dynamically by hostname, not IP.
| Hostname | Protocol | Description |
|---|---|---|
relay.caresuite.ch | HTTP(S) (Port 80 and 443) | Updates, Licensing, Mailing |
CareSuite App
If the CareSuite App is used, the following hostnames need to be accessible for the App to work:
| Hostname | Protocol | Description |
|---|---|---|
fcm.googleapis.com | HTTP(S) (Port 80 and 443) | Firebase Cloud Messaging See notes below |
Gets Cloud Backups
If Gets Cloud Backups are used, the following hostnames need to be accessible for the backup to work:
| Hostname | Protocol | Description |
|---|---|---|
europe-west1-gec-monitor-635bf.cloudfunctions.net | HTTP(S) (Port 80 and 443) | Gets Cloud Backups |
Why is a GUI recommended?
Our system integrators often use the CareSuite Server as a jump host to manage other Gets components via remote access (like TeamViewer). These components are configured via a web interface, which makes a graphical user interface necessary.
If you can provide other means for our integrators to access your network (VPN, Windows Remote Desktop, Jump hosts) and give access to a graphical user interface, the CareSuite software can be installed without a GUI. The CareSuite Server must be accessible via SSH from a jump host in this scenario.
Please contact the system integrator to discuss the requirements and find a solution that integrates well into your IT infrastructure.
Firebase Cloud Messaging
Firebase Cloud Messaging is only required if the CareSuite App is used.
The CareSuite App tries to keep all data locally in the network. We do, however, use Firebase Cloud Messaging as a fallback notification method if a device is currently not reachable in the local network.
To use this fallback method, the CareSuite server and all App clients must get access to the fcm.googleapis.com endpoint.