MedITEX utilizes a client/server architecture with Firebird 2.5 as its database.

The following diagram shows one example of configuration where MedITEX could be installed.

 

Server-client requirements

The table below describes the recommended and minimum requirements for installing MedITEX, as well as additional information regarding some of the applications running on the server and clients to ensure the good quality of services and the proper functioning of MedITEX.

It is recommended that the server provided is dedicated exclusively for the use of MedITEX. Having other applications running alongside MedITEX can compromise the overall functionality of the system.

The optimal solution for maximum performance is a dedicated database server built in an SSD, which is not virtualized.
An SSD (especially enterprise SSD) allows much more IOPS.
Using a Firebird server with the database on an external SAN/NAS is not recommended, since the speed of a Firebird database server depends on the speed of access to individual 4k blocks on the device. External SAN/NAS drives are great for transferring hundreds of MB of data from one file location to another. However the Firebird server transfers hundreds of thousands of small pages between memory and physical hard disk found on different file offsets.
Please consider the access time of a mechanical hard drive to be the limiting factor in performance. A commit writes data in very different file offsets. RAID is not found to improve this limitation as the head position of the hard disk must move in the same way.

	Recommended requirements (depending on number of clients): OS: Windows Server 2008 or later; Primary SSD: 256 GB  for Windows and MedITEX applications; Secondary hard disk: 300 - 500 GB free space for file storage and backup; 1 Hot Plug SSD for an active shadow; CPU: multi-core processor 2 GHz. Intel Pentium i3, i5 or greater; RAM: 8-16 GB. When the database server and shadow SSDs reach an age of 2 years, they should be replaced to avoid unplanned failure (in server systems, we recommend the same for classic hard drives). The size of the SSDs should be 400% of your current database size or higher. Minimum requirements: OS: Windows Server 2003; Hard disk: 120 GB free space; CPU: single-core 3 GHz; RAM Memory: 4GB or more.
	File based repository: All documents, pictures and common settings are stored on this location.
	Backup Service: Schedules and creates backup of database and repository.
	Recommended requirements: OS: Windows 7 or later; Hard disk: 1GB free space; CPU: multi-core processor 2 GHz; RAM: 4 GB or more; Graphics: 1680x1050. Minimum hardware requirements: OS: Windows 7; Hard disk: 1GB free space; CPU: single-core 2 GHz; RAM: 2 GB or more; Graphics: 1280x1024.
	MS Office Integration: All letters based on MS Word templates. Minimum requirement: MS Office 2003. Alternative module for letters based on WordPad.
	TWAIN: TWAIN is used for importing patient photos, ultrasound images (Frame Grabber), etc.
	Voice: Record and play voice messages.

 

Note that the experience with MedITEX for the client will depend on the speed of the network. All clients must be wired connected to the network and it is recommended the use of 1 Gbps speed. The recommended internet connection should be 16 MB download and 1 MB upload.

 

Terminal server requirements

For terminal server architecture a more powerful server is required.

	Recommended requirements (depending on number of clients): OS: Windows Server 2008 or later; Hard disk: 300 - 500 GB free space; CPU: multi-core processor 2 GHz; RAM: 16-32 GB.
	Minimum requirements: Graphics: 1280x1024; 100 Kilobytes per second for each session; Each increase in screen resolution or color depth requires more bandwidth per session; RAM: 100 MB per session.

 

The line should be able to support other connections as well, without impairing terminal server connections. In other words, it should be capable of serving internet access of other clients in parallel to terminal sessions - must be projected as broader than "Number of TS x Speed per session". Upload speed of the server is critical, because the server is serving all open sessions in parallel, and for each one of them the required speed must be ensured. Clients should use newest version of RDC (6.1 or higher), because Microsoft has significantly reduced the bandwidth consumptions of newer RDC version in comparison to older ones. The server itself should be capable of serving multiple terminal sessions without problems. Line should be stable and without interruptions.

Back to Administrators Support

Back to top