Technical Requirements for custo diagnostic server and custo diagnostic clients in custo diagnostic 5.1.x.
This document is to be used for Standard or Minimum Requirements.
Note: This Release is not suitable for Clinical Environments.
(64bit Windows supported only)
Note: Windows Server Core Editions are also supported!
Note:
As of custo diagnostic 5.1.x, the data of the trend files were transferred to the logical database and the trend files were removed. In addition, all measured values (export elements) for all evaluations are saved in the logical database permanently (thus a BigData analysis can be performed.). Explanation "logical database": The custo diagnostic database consists of 2 parts. On the one hand of the cst files in which the raw data of evaluations are saved and on the other hand of a logical database (H2, MS-SQL or MariaDB) in which all the other data (users, patients, settings, AuditTrail etc.) are saved. These data volumes are additionally saved in the logical database per generated evaluation. The logical database will grow faster than in all previous versions. This has to be taken into account, particularly when the AuditTrail is activated. However, this also means that if the logical database exceeds the 10 GB size, Microsoft SQL Server Express cannot be used anymore. The SQL database must then be relocated to a Microsoft SQL Server (Attention: Microsoft SQL Server must be bought and licenced!). custo diagnostic 5.1.x now also supports MariaDB, a GPL-licenced DB system (see: https://mariadb.com/kb/en/library/licensing-faq). This DB system can also be used commercially free of charge. In order to relocate an existing database to another DB system (e. g. MS-SQL to MariaDB), the custo diagnostic server has implemented a database converter which can perform this task. You can find information here: https://www.customed.de/docs/x/EYDyAQ
(32bit / 64bit Windows supported)
Note: Windows Server can be used as a "View 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.
All USB based custo med Devices working with USB 1.1 or USB 2.0 Specification.
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.
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.
In case Microsoft SQL Database is used:
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. |