Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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. For Clinical Environments please refer to this Page.

Note: This Release is the first release for Clinical Environments.

...

(64bit Windows supported only)

  • Microsoft Windows 7, SP1Microsoft Windows 8.1
  • Microsoft Windows 10 (for full compatibility guide see here)
  • Microsoft Windows Server 2012
  • Microsoft Windows Server 2012 R2
  • Microsoft Windows Server 2016
  • Microsoft Windows Server 2019

...

  • Microsoft Windows 8.1
  • Microsoft Windows 10 (for full compatibility guide see here)
  • Microsoft Windows Server 2012
  • Microsoft Windows Server 2012 R2
  • Microsoft Windows Server 2016
  • Microsoft Windows Server 2019

...

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

...

  • 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)

MariaDB for Patient and Examination Information

  • No special conditions necessary if shipped MariaDB Installer is used

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 ECG15MB60MB
ABPM128KB512KB
ABPM/Holter combi20MB25MB
Resting ECG200KB (10 Sek.)unlim.
Stress ECG20MB (20 Min.)unlim.
CPET20MB (20 Min.)unlim.
Spirometry50KB256KB
Cardiac Rehab Session6MB (45 Min.)unlim.
custo kybe15MB (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.