View source for First Steps Before Using MedITEX

<p>&nbsp;</p>
<h2>Personnel Organization</h2>
<p>In an IVF clinic you have different groups of personnel like doctors, physicians, embryologists, nurses, secretaries... All of them are dealing with information and documents, but each group will need to work with a different access to MedITEX software solutions because of various levels of responsibilities.</p>
<p>To ensure that these different levels of permissions will not be exceeded, each user needs unique login data and special defined rights.<br />The secretaries for example, speak with the patient the first time by registration or a telephone call. They document the private information about the patient. Later the doctor adds the results of the examination. The laboratory staff has no possibilities to change clinical information, just to complete the missing data.</p>
<p>The hospital workflow differs in each clinic. It is important to know about these internal processes and their command structure before using MedITEX software solutions, so assigning rights is getting much easier.</p>
<p>This image shows a typical IVF clinic:</p>
<table style="margin-left: auto; margin-right: auto;" border="0">
<tbody>
<tr>
<td>[[Image:krank11png.png|none|740px|thumb|left|link=http://wiki.meditex-software.com/images/krank11png.png]]</td>
</tr>
</tbody>
</table>
<p>&nbsp;</p>
<h2>Technical Requirements</h2>
<p>Before the installation begins, it is needful that your IT admins prepare all the necessary hardware (servers and clients) and ensure fast and reliable network connections.<br />For guarantee this, please assign one responsible person who will get in contact with us.</p>
<p>&nbsp;</p>
<h3>3 Steps of Installation Process</h3>
<p>The installation process is divided in <strong><span style="text-decoration: underline;">3 steps</span></strong>: Preparation, Installation and Setup of satellite location.</p>
<p>&nbsp;</p>
<h4>1. Step: Preparation</h4>
<p>- We need a physical or virtual server with Win Server OS (2003+) installed and running</p>
<p>- Internal and VPN connections to the server should be ensured and prepared</p>
<p>- Remote access over internet to the server should be possible</p>
<p>These tasks should be performed by your IT responsible, whom our support member will provide with information and support.</p>
<p>&nbsp;</p>
<h4>2. Step: Installation</h4>
<p>In order to begin with the installation (step 2) it is absolutely necessary that the requirements from the step 1 <strong>are fulfilled <span style="text-decoration: underline;">before</span></strong>.</p>
<p>After the server is prepared, our team will access it remotely and test if everything is ready for the installation.<br />During the installation we will need constant support from your IT  responsible, and a possibility to consult a medical specialist from your  team who knows all the staff and their roles, medical procedures  performed, and other special details which our support member will have  to configure in MedITEX.</p>
<p>&nbsp;</p>
<h4>3. Step: Setup of satellite location</h4>
<p>Setup of MedITEX access from satellite clinic to central data server, locally in satellite clinic.</p>
<p>&nbsp;</p>
<h2>MedITEX Software Technical Specification - Overview</h2>
<table style="margin-left: auto; margin-right: auto;" border="0">
<tbody>
<tr>
<td>
<p style="text-align: center;">[[Image:Tech1.png|none|740px|thumb|left|link=http://wiki.meditex-software.com/images/Tech1.png]]</p>
</td>
</tr>
</tbody>
</table>
<p>&nbsp;</p>
<table style="margin-left: auto; margin-right: auto;" border="0" width="615" height="625">
<tbody>
<tr>
<td style="text-align: center;"><img src="/images/Tech2.png" alt="" /></td>
<td>
<p><span style="text-decoration: underline;"><strong>Server (minimum requirement)</strong></span></p>
<p>1. OS: Windows Server 2000, 2003 Recommended: Win Server 2008<br />2. Hard disk: &gt; 2 GB free space<br />3. CPU: &gt; 1500 Mhz<br />4. RAM Memory: &gt;= 4GB</p>
</td>
</tr>
<tr>
<td><img style="display: block; margin-left: auto; margin-right: auto;" src="/images/Tech3.png" alt="" /></td>
<td>
<p><strong><span style="text-decoration: underline;">Database</span></strong></p>
<p>Firebird SQL Server 2.x</p>
<p>&nbsp;</p>
</td>
</tr>
<tr>
<td><img style="display: block; margin-left: auto; margin-right: auto;" src="/images/Tech4.png" alt="" /></td>
<td>
<p><strong><span style="text-decoration: underline;">File based repository; Sharing of file space for all clients</span></strong></p>
<p>All documents, pictures and common settings are stored here<br />Hard disk: Depends on the amount of data &gt; GB<strong><span style="text-decoration: underline;"><br /></span></strong></p>
</td>
</tr>
<tr>
<td><img style="display: block; margin-left: auto; margin-right: auto;" src="/images/Tech5.png" alt="" /></td>
<td>
<p><strong><span style="text-decoration: underline;">Backup Service</span></strong></p>
<p>Schedules and create Backups<span style="text-decoration: underline;">&nbsp;</span> of Database and Repository<strong><span style="text-decoration: underline;"><br /></span></strong></p>
</td>
</tr>
<tr>
<td><img style="display: block; margin-left: auto; margin-right: auto;" src="/images/Tech7.png" alt="" /></td>
<td>
<p style="text-align: left;"><strong><span style="text-decoration: underline;">Minimum hardware requirement:</span></strong></p>
<p style="text-align: left;">1. OS: Windows 2000, XP, Vista, 7<br />2. Hard disk: &gt; 1GB free space<br />3. CPU: &gt; 1000 MHz<br />4. RAM Memory: &gt; 512 MB<br />5. Graphic: 1024x768</p>
</td>
</tr>
<tr>
<td><img style="display: block; margin-left: auto; margin-right: auto;" src="/images/Tech8.png" alt="" /></td>
<td>
<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. Min required MS Office 2003<br />Alternative module for letters based on WordPad</p>
</td>
</tr>
<tr>
<td><img style="display: block; margin-left: auto; margin-right: auto;" src="/images/Tech9.png" alt="" /></td>
<td>
<p><strong><span style="text-decoration: underline;">TWAIN</span></strong></p>
<p>TWAIN is used for Importing Patient photos, Ultrasound Images <strong><span style="text-decoration: underline;"><br /></span></strong>(Frame Grabber), etc.<strong><span style="text-decoration: underline;"><br /></span></strong></p>
</td>
</tr>
<tr>
<td><img style="display: block; margin-left: auto; margin-right: auto;" src="/images/Tech10.png" alt="" /></td>
<td>
<p><span style="text-decoration: underline;"><strong>Voice</strong></span></p>
<p>Record and Play Voice Messages; Using standard Windows equipment</p>
</td>
</tr>
<tr>
<td><img style="display: block; margin-left: auto; margin-right: auto;" src="/images/Tech12.png" alt="" /></td>
<td>
<p><span style="text-decoration: underline;"><strong>Terminal</strong></span><span style="text-decoration: underline;"><strong> Server</strong></span><span style="text-decoration: underline;"><strong> Connection</strong></span><span style="text-decoration: underline;"><strong> (minimum</strong></span><span style="text-decoration: underline;"><strong> requirement)</strong></span></p>
<p><br />1. 1024x768@16 bit color: ca. 30 Kbps per session*<br />2. Each increase in screen resolution or color depth requires about<br />&nbsp;&nbsp;&nbsp; 3-4 Kbps more bandwidth per session<br />3. RAM: 100 MB per session</p>
</td>
</tr>
</tbody>
</table>
<p>&nbsp;</p>
<p><em>*Over a Terminal Server RDP connection, there are multiple applications (for example video, clipboard, printer output etc.) that send data over the connection from server to client. On a congested or high latency connection these applications compete for available bandwidth. As a result, important graphics data, such as the location of a window the user moves on the desktop, has to compete with data transmitted in the background, like a print job or a file copy. This problem manifests itself most severely when printing a large document over such a connection. The printer data competes for available bandwidth with the video rendering, thus deteriorating the graphics rendering significantly. Drive mappings and the applications accessed have an effect, as well. </em></p>
<p><em>A proposed &ldquo;minimum&rdquo; number for RDP bandwidth requirements of around 30Kbps per user depend a lot on the features used, screen resolution and color depth and the frequency of &nbsp;print jobs. This 30Kbps number does not include other activity that may take place on the network: http, smtp, rpc, VoIP, etc. So plan for more. </em></p>
<p><em>With an Internet VPN, all the traffic on the WAN connection is in competition with each other, unless you have excess bandwidth. Using MPLS, you can prioritize your RDP sessions to assure stable performance for all users on your WAN, without the need of unnecessarily wasting money on excess bandwidth.</em></p>
<table style="float: right;" border="0">
<tbody>
<tr>
<td style="text-align: right;">
<p><span><a style="font-size: small;" href="/index.php?title=Main_Page">Back to MedITEX products</a></span></p>
</td>
<td style="text-align: right;"><a href="#top">Back to top</a></td>
</tr>
</tbody>
</table>