System Requirements
Technical Requirements for custo diagnostic server and custo diagnostic clients in custo diagnostic 5.2.x.
This document is to be used for Standard or Minimum Requirements.
Note: This Release is the first release for Clinical Environments.
Server
Hardware / Virtual Setup
- HDD min. 250 GB – depending on usage (see below)
- RAM min. 4 GB
- 2x (v)CPU min. 1.5 GHz
Supported Operating Systems
(64bit Windows supported only)
- Microsoft Windows 8.1
- Microsoft Windows 10 (for fully compatibility guide see here)
- Microsoft Windows Server 2012
- Microsoft Windows Server 2012 R2
- Microsoft Windows Server 2016
- Microsoft Windows Server 2019
Note: Windows Server Core Editions are also supported!
Supported Database Systems and Database Servers
- Microsoft SQL Server 2008 and above (32bit and 64bit) (recommended)
- All Editions: Express, Enterprise, Datacenter, Business Intelligence, Standard, Workgroup, Web
- Microsoft SQL Server (except Express Edition) must be provided/installed/licenced by the customer
- Express Edition is not recommended for production environment
- MariaDB (included in custo diagnostic Installer) (possible)
- H2 Database (included in custo diagnostic Installer) (not recommended in a production environment)
Client
Hardware / Virtual Setup
- HDD min. 5 GB
- RAM min. 4 GB
- 2x (v)CPU min. 1,5 GHz
Supported Operating Systems
(32bit / 64bit Windows supported)
- Microsoft Windows 8.1
- Microsoft Windows 10 (for fully compatibility guide see here)
- Microsoft Windows Server 2012
- Microsoft Windows Server 2012 R2
- Microsoft Windows Server 2016
- Microsoft Windows Server 2019
Note: Windows Server can be used as a "View Client" or Windows Terminal Server - but not for an acquisition workstation.
Ports / Connections
- accessible USB Ports; Number depending on custo med Devices in use
- Sufficient WiFi quality for mobile applications
- BT Test with custo med Devices passed, if internal BT should be used
Requirements for Bluetooth Connectivity
All Bluetooth devices of custo med are working at least with Bluetooth 2.0 EDR specification and are Class-2 devices - which means maximum of 10 meter distance from the device to the PC. Do not use device and custo diagnostic application PC in different rooms. In circumstances where this is required (e.g. bedside ECG in infectious environments to avoid the contamination of the device trolley) please keep both in line of sigh.
Requirements for USB Connectivity
All USB based custo med Devices working with USB 1.1 or USB 2.0 Specification.
Satellite Systems
Satellite Systems are mobile ECG systems, which contain the custo diagnostic server and custo diagnostic client on the same windows host and must fulfill Client and Server Requirements. Satellite Systems can be used in non reliable network situations to acquire ECG recordings locally. The synchronisation between local custo diagnostic server and central custo diagnostic server is done automatically (http/https), when the network is available. Only 64bit Operating Systems are supported.
System Architecture
custo diagnostic server is a Apache Tomcat based Application Server. The process responds on ReST / http / https requests and access the database and the raw data directory.
MariaDB for Patient and Examination Information
- No special conditions necessary if shipped MariaDB Installer is used
Microsoft SQL Database for Patient and Examination Information
In case Microsoft SQL Database is used:
- SQL Server Instance must be configured to fixed Port (Default: 1433)
- SQL credentials must be configured to "SQL Server and Windows Authentication Mode"
- SQL User required to be DB Owner
- SQL User must have Server Roles: public; read on Master DB
- Location: free of choice (could be a dedicated/separate SQL Server)
Raw Data Directory
- 100 GB are good for a start, necessary examination file storage can be calculated based on the table below, based on usage
- Apache Tomcat Service User must have write access to this Directory
- Directory should be (very recommended) a local Directory on the Computer where custo diagnostic server is running
- Location: free of choice; could be a dedicated Windows File Server - but NAS, Samba or CIFS on NetApp is not recommended!
- Data Directory must only be accessible by Apache Tomcat Service User
Examination file sizes for storage usage calculation:
Product | File size typical ca. | File size max. |
|---|---|---|
| Holter ECG | 15MB | 60MB |
| ABPM | 128KB | 512KB |
| ABPM/Holter combi | 20MB | 25MB |
| Resting ECG | 200KB (10 Sek.) | unlim. |
| Stress ECG | 20MB (20 Min.) | unlim. |
| CPET | 20MB (20 Min.) | unlim. |
| Spirometry | 50KB | 256KB |
| Cardiac Rehab Session | 6MB (45 Min.) | unlim. |
| custo kybe | 15MB (24h) | unlim. |
Network connectivity
- 1000 MBit LAN Connection is recommended
- Firewall setup (by Administrator): Server Computer must only be accessible by Administrators. All clients access the custo diagnostic server by using http/https through a TCP Port only (Default: 8080).
- For a WiFi based use of ECG recordings a stable, constant WiFi connection is necessary during recording and access. (In environments of unstable / not constant WiFi connections custo supplies dedicated solutions. Please ask your dealer in this case.) A recording of a holter ECG produces up to 10 MByte of data. Please consider this at your WiFi planning.