Technical Requirements for server and clients in custo diagnostic 5.x - dedicated to a clinical environment.
These requirements refer to custo diagnostic 5.5.x clinical and above.
(64bit Windows supported only)
Note: Windows Server Core Editions are also supported!
Note: The H2 database which comes included with custo diagnostic 5.2.x Installer is not supported in a production environment of custo diagnostic 5.2.x clinical.
(32bit / 64bit Windows supported)
Windows Server can be used as a client or Windows Terminal Server - but not for an acquisition workstation.
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.
Satellite Systems are mobile ECG systems, which contain the custo diagnostic server and custo diagnostic client on the same windows host. 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. Windows 8.1 is not supported for satellite systems.
custo diagnostic server is a Apache Tomcat based service. The process responds on ReST / http / https requests and access the database and the raw data directory.
In case, Microsoft SQL Database should be used (instead of mariaDB):
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. |
For a WiFi based use of ECG recordings a stable, constant WiFi connection is necessary during recording and access.
Firewall setup (by clinic administrator): Server Computer must only be accessible by Administrators and Apache Tomcat User. All clients only access the custo diagnostic server by using http/https.
(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.
Always accessible connection, based on Teamviewer, VPN dial-in or VPN-site-to-site with RDP access to the dedicated server where the custo diagnostic server is running is highly recommended during installation project and useful for maintenance.
On-demand software may also be used: Teamviewer, WebEx or GoToMeeting sessions. On-demand sessions must be provided on short-notice (10 minutes) during installation project.
Except when otherwise stipulated in written form, the clinic is the operator of the system and takes care for typical operator tasks.
Regarding the maintenance of hardware and software components, the following aspects should be monitored by the operator:
custo diagnostic server is a windows service based on Apache Tomcat and a database server.
General IT security tasks are part of the operators maintenance and operating:
There is no general limitation for the usage of virus scanners.
In case of misbehavior or errors, custo med may ask the operator to limit/change the function of the virus scanner.
Subject to change without notice.