MedITEX Software Technical Requirements

From MedITEX - Wiki

(Difference between revisions)
Jump to: navigation, search
 
(16 intermediate revisions by 3 users not shown)
Line 1: Line 1:
−
<p><strong>MedITEX</strong> utilizes a client/server architecture with <strong>Firebird 2.5</strong> as its database.</p>
+
<p><strong>MedITEX</strong> utilizes a client/server architecture with <strong>Firebird</strong>&nbsp;as its database.</p>
 
<p>The following diagram shows one example of configuration where <strong>MedITEX </strong>could be installed.</p>
 
<p>The following diagram shows one example of configuration where <strong>MedITEX </strong>could be installed.</p>
 
<table style="margin-left: auto; margin-right: auto;" border="0">
 
<table style="margin-left: auto; margin-right: auto;" border="0">
Line 32: Line 32:
 
<p><strong><span style="text-decoration: underline;">Recommended requirements (depending on number of clients):</span></strong></p>
 
<p><strong><span style="text-decoration: underline;">Recommended requirements (depending on number of clients):</span></strong></p>
 
<ol>
 
<ol>
−
<li>OS: Windows Server 2008 or later;</li>
+
<li>OS: Windows Server 2016 or later;</li>
 
<li>Primary SSD: 256 GB&nbsp; for Windows and MedITEX applications;</li>
 
<li>Primary SSD: 256 GB&nbsp; for Windows and MedITEX applications;</li>
 
<li>Secondary hard disk: 300 - 500 GB free space for file storage and backup;</li>
 
<li>Secondary hard disk: 300 - 500 GB free space for file storage and backup;</li>
 
<li>1 Hot Plug SSD for an active shadow;</li>
 
<li>1 Hot Plug SSD for an active shadow;</li>
−
<li>CPU: multi-core processor 2 GHz. Intel Pentium i3, i5 or greater;</li>
+
<li>CPU: multi-core processor 2 GHz. Intel i7, i9 or greater;</li>
−
<li>RAM: 8-16 GB.</li>
+
<li>Processor Architecture: x64;</li>
 +
<li>RAM: 16-32 GB.</li>
 
</ol>
 
</ol>
 
<p><em>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).</em><br /><em>The size of the SSDs should be 400% of your current database size or higher.</em></p>
 
<p><em>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).</em><br /><em>The size of the SSDs should be 400% of your current database size or higher.</em></p>
Line 43: Line 44:
 
<p><span style="text-decoration: underline;"><strong>Minimum requirements:</strong></span></p>
 
<p><span style="text-decoration: underline;"><strong>Minimum requirements:</strong></span></p>
 
<ol>
 
<ol>
−
<li>OS: Windows Server 2003;</li>
+
<li>OS: Windows Server 2016;</li>
 
<li>Hard disk: 120 GB free space;</li>
 
<li>Hard disk: 120 GB free space;</li>
 
<li>CPU: single-core 3 GHz;</li>
 
<li>CPU: single-core 3 GHz;</li>
−
<li>RAM Memory: 4GB or more.</li>
+
<li>Processor Architecture: x64;</li>
−
</ol><em>&nbsp;</em><ol> </ol></td>
+
<li>RAM Memory: 16GB or more.</li>
 +
</ol></td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
Line 68: Line 70:
 
<p style="text-align: left;"><strong><span style="text-decoration: underline;">Recommended requirements:</span></strong></p>
 
<p style="text-align: left;"><strong><span style="text-decoration: underline;">Recommended requirements:</span></strong></p>
 
<ol>
 
<ol>
−
<li>OS: Windows 7 or later;</li>
+
<li>OS: Windows 10 or later;</li>
 
<li>Hard disk: 1GB free space;</li>
 
<li>Hard disk: 1GB free space;</li>
 
<li>CPU: multi-core processor 2 GHz;</li>
 
<li>CPU: multi-core processor 2 GHz;</li>
Line 76: Line 78:
 
<p style="text-align: left;"><strong><span style="text-decoration: underline;">Minimum hardware requirements:</span></strong></p>
 
<p style="text-align: left;"><strong><span style="text-decoration: underline;">Minimum hardware requirements:</span></strong></p>
 
<ol>
 
<ol>
−
<li>OS: Windows 7;</li>
+
<li>OS: Windows 10;</li>
 
<li>Hard disk: 1GB free space;</li>
 
<li>Hard disk: 1GB free space;</li>
 
<li>CPU: single-core 2 GHz;</li>
 
<li>CPU: single-core 2 GHz;</li>
Line 87: Line 89:
 
<td>
 
<td>
 
<p style="text-align: left;"><span style="text-decoration: underline;"><strong>MS Office Integration:</strong></span></p>
 
<p style="text-align: left;"><span style="text-decoration: underline;"><strong>MS Office Integration:</strong></span></p>
−
<p style="text-align: left;">All letters based on MS Word templates. Minimum requirement: MS Office 2003.<br />Alternative module for letters based on WordPad.</p>
+
<p style="text-align: left;">All letters based on MS Word templates. Minimum requirement: MS Office 2016 or later.<br />Alternative module for letters based on WordPad.</p>
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 114: Line 116:
 
<p>Note that the experience with <strong>MedITEX </strong>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.</p>
 
<p>Note that the experience with <strong>MedITEX </strong>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.</p>
 
<p>The recommended internet connection should be 16 MB download and 1 MB upload.</p>
 
<p>The recommended internet connection should be 16 MB download and 1 MB upload.</p>
 +
</td>
 +
</tr>
 +
</tbody>
 +
</table>
 +
<p>&nbsp;</p>
 +
<table border="0">
 +
<tbody>
 +
<tr>
 +
<td><img src="/images/hint48.png" alt="" width="48" height="48" /></td>
 +
<td>
 +
<p>It is important to know that a Firebird database server should be a  dedicated server and should only be responsible for the Firebird  database service in order to ensure maximum performance.</p>
 +
<p>Virtual servers  lose between 20% and 80 % of their speed under a high load on a VM. Any  advantage of a VM-based Firebird Server will be paid for dearly by all  employees waiting additional time to carry out and complete their jobs.</p>
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 128: Line 142:
 
<p><strong><span style="text-decoration: underline;">Recommended requirements (depending on number of clients):</span></strong></p>
 
<p><strong><span style="text-decoration: underline;">Recommended requirements (depending on number of clients):</span></strong></p>
 
<ol>
 
<ol>
−
<li>OS: Windows Server 2008 or later;</li>
+
<li>OS: Windows Server 2016 or later;</li>
 
<li>Hard disk: 300 - 500 GB free space;</li>
 
<li>Hard disk: 300 - 500 GB free space;</li>
 
<li>CPU: multi-core processor 2 GHz;</li>
 
<li>CPU: multi-core processor 2 GHz;</li>
Line 164: Line 178:
 
</tbody>
 
</tbody>
 
</table>
 
</table>
 +
<p>&nbsp;</p>
 +
<h2>Server configuration</h2>
 +
<table style="margin-left: auto; margin-right: auto;" border="0" width="447" height="181">
 +
<tbody>
 +
<tr>
 +
<td>
 +
<p>The server should be configured in the following way:</p>
 +
<ul>
 +
<li>File share &ndash; <em>MedITEX applications</em>.</li>
 +
<li>Central file storage &ndash;<em> letters, reports, images, etc.</em></li>
 +
<li>Windows services &ndash; <em>DICOM, HL7, etc.</em></li>
 +
<li>Database services &ndash; <em>FirebirdSQL Server</em></li>
 +
</ul>
 +
</td>
 +
</tr>
 +
</tbody>
 +
</table>
 +
<p>&nbsp;</p>
 
<table style="float: right;" border="0">
 
<table style="float: right;" border="0">
 
<tbody>
 
<tbody>

Latest revision as of 08:57, 11 April 2024

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

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

<tbody> </tbody>

<img src="/images/Tech1.png" alt="" width="740" height="548" />

 

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.

<tbody> </tbody>
<img src="/images/hint48.png" alt="" width="48" height="48" />

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.

<tbody> </tbody>
<img src="/images/Tech2.png" alt="" />

Recommended requirements (depending on number of clients):

  1. OS: Windows Server 2016 or later;
  2. Primary SSD: 256 GB  for Windows and MedITEX applications;
  3. Secondary hard disk: 300 - 500 GB free space for file storage and backup;
  4. 1 Hot Plug SSD for an active shadow;
  5. CPU: multi-core processor 2 GHz. Intel i7, i9 or greater;
  6. Processor Architecture: x64;
  7. RAM: 16-32 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:

  1. OS: Windows Server 2016;
  2. Hard disk: 120 GB free space;
  3. CPU: single-core 3 GHz;
  4. Processor Architecture: x64;
  5. RAM Memory: 16GB or more.
<img style="display: block; margin-left: auto; margin-right: auto;" src="/images/Tech4.png" alt="" />

File based repository:

All documents, pictures and common settings are stored on this location.
<img style="display: block; margin-left: auto; margin-right: auto;" src="/images/Tech5.png" alt="" />

Backup Service:

Schedules and creates backup of database and repository.
<img style="display: block; margin-left: auto; margin-right: auto;" src="/images/Tech7.png" alt="" />

Recommended requirements:

  1. OS: Windows 10 or later;
  2. Hard disk: 1GB free space;
  3. CPU: multi-core processor 2 GHz;
  4. RAM: 4 GB or more;
  5. Graphics: 1680x1050.

Minimum hardware requirements:

  1. OS: Windows 10;
  2. Hard disk: 1GB free space;
  3. CPU: single-core 2 GHz;
  4. RAM: 2 GB or more;
  5. Graphics: 1280x1024.
<img style="display: block; margin-left: auto; margin-right: auto;" src="/images/Tech8.png" alt="" />

MS Office Integration:

All letters based on MS Word templates. Minimum requirement: MS Office 2016 or later.
Alternative module for letters based on WordPad.
<img style="display: block; margin-left: auto; margin-right: auto;" src="/images/Tech9.png" alt="" />

TWAIN:

TWAIN is used for importing patient photos, ultrasound images (Frame Grabber), etc.
<img style="display: block; margin-left: auto; margin-right: auto;" src="/images/Tech10.png" alt="" />

Voice:

Record and play voice messages.

 

<tbody> </tbody>
<img src="/images/hint48.png" alt="" width="48" height="48" />

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.

 

<tbody> </tbody>
<img src="/images/hint48.png" alt="" width="48" height="48" />

It is important to know that a Firebird database server should be a dedicated server and should only be responsible for the Firebird database service in order to ensure maximum performance.

Virtual servers lose between 20% and 80 % of their speed under a high load on a VM. Any advantage of a VM-based Firebird Server will be paid for dearly by all employees waiting additional time to carry out and complete their jobs.

 

Terminal server requirements

For terminal server architecture a more powerful server is required.

<tbody> </tbody>
<img src="/images/Tech2.png" alt="" />

Recommended requirements (depending on number of clients):

  1. OS: Windows Server 2016 or later;
  2. Hard disk: 300 - 500 GB free space;
  3. CPU: multi-core processor 2 GHz;
  4. RAM: 16-32 GB.
<img style="display: block; margin-left: auto; margin-right: auto;" src="/images/Tech12.png" alt="" />

Minimum requirements:

  1. Graphics: 1280x1024;
  2. 100 Kilobytes per second for each session;
  3. Each increase in screen resolution or color depth requires more bandwidth per session;
  4. RAM: 100 MB per session.

 

<tbody> </tbody>
<img src="/images/hint129.png" alt="" width="129" height="129" />
  • 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.

 

Server configuration

<tbody> </tbody>

The server should be configured in the following way:

  • File share – MedITEX applications.
  • Central file storage – letters, reports, images, etc.
  • Windows services – DICOM, HL7, etc.
  • Database services – FirebirdSQL Server

 

<tbody> </tbody>

<a style="font-size: small;" href="/index.php?title=Administrators_Support">Back to Administrators Support
</a>

 <a href="#top">Back to top</a>