First Steps Before Using MedITEX

From MedITEX - Wiki

(Difference between revisions)
Jump to: navigation, search
Line 51: Line 51:
 
<td>
 
<td>
 
<p><strong><span style="text-decoration: underline;">Backup Service</span></strong></p>
 
<p><strong><span style="text-decoration: underline;">Backup Service</span></strong></p>
<p>Schedules and create Backups<span style="text-decoration: underline;"></span> of Database and Repository<strong><span style="text-decoration: underline;"><br /></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>
 
</td>
 
</tr>
 
</tr>
Line 91: Line 91:
 
</tbody>
 
</tbody>
 
</table>
 
</table>
 +
<p><img src="/images/SternchenZusatz.png" alt="" width="756" height="352" /></p>
 
<p>&nbsp;</p>
 
<p>&nbsp;</p>
 
<p>&nbsp;</p>
 
<p>&nbsp;</p>

Revision as of 11:18, 30 October 2013

 

 

Contents

Personnel Organization

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.
To ensure that these different levels of permissions will not be exceeded, each user needs unique login data and special defined rights.
The  secretaries for example, speak with the patient the first time by registration or a telephone call. They document the privat informations 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.
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 more easier.

 

krank11png.png

 

Technical Requirements

Before the installation beginns, it is needfully that your IT admins prepare all the necessary hardware (servers and clients) and ensure fast and reliable network connections.
For guarantee this, please assign one responsible person who will get in contact with us.

3 Steps of Installation Process

The installation process is divided in 3 steps : Preparation, Installation and Setup of satellite location.

1. Step: Preparation

- We need a physical or virtual server with Win Server OS(2003+) installed and running

- Internal and VPN connections to the server should be ensured and prepared

- Remote access over internet to the server should be possible

These tasks should be performed by your IT responsible, whom our support member will provide with information and support.

2. Step: Installation

In order to begin with the installation (step 2) it is absolutely necessary that the requirements from the step 1 are fulfilled before.
After the server is prepared, our team will access it remotely and test if everything is ready for the installation.
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.

3. Step: Setup of satellite location

Setup of MedITEX access from satellite clinic to central data server, locally in satellite clinic.

MedITEX Software Technical Specification - Overview

 

Tech1.png

 

<tbody> </tbody>
<img style="display: block; margin-left: auto; margin-right: auto;" src="/images/Tech2.png" alt="" width="156" height="243" />

Server (mimimum requirement)

1. OS: Windows Server 2000, 2003 Recommended: Win Server 2008
2. Hard disk: > 2 GB free space
3. CPU: > 1500 Mhz
4. RAM Memory: >= 4GB

<img style="display: block; margin-left: auto; margin-right: auto;" src="/images/Tech3.png" alt="" width="90" height="120" />

Database

Firebird SQL Server 2.x

 

<img style="display: block; margin-left: auto; margin-right: auto;" src="/images/Tech4.png" alt="" width="90" height="74" />

File based repository; Sharing of file space for all clients

All documents, pictures and common settings are stored here
Hard disk: Depends on the amount of data > GB

<img style="display: block; margin-left: auto; margin-right: auto;" src="/images/Tech5.png" alt="" width="88" height="60" />

Backup Service

Schedules and create Backups  of Database and Repository

<img style="display: block; margin-left: auto; margin-right: auto;" src="/images/Tech7.png" alt="" width="108" height="70" />

Minimum hardware requirement:

1. OS: Windows 2000, XP, Vista, 7
2. Hard disk: > 1GB free space
3. CPU: > 1000 MHz
4. RAM Memory: > 512 MB
5. Graphic: 1024x768

<img style="display: block; margin-left: auto; margin-right: auto;" src="/images/Tech8.png" alt="" width="89" height="59" />

MS Office Integration

All letters based on MS Word tamplates. Min required MS Office 2003
Alternative module for letters based on Wordpad

<img style="display: block; margin-left: auto; margin-right: auto;" src="/images/Tech9.png" alt="" width="87" height="60" />

TWAIN

TWAIN is used for Importing Patient phots, Ultrasound Images
(FrameGrabber), ect.

<img style="display: block; margin-left: auto; margin-right: auto;" src="/images/Tech10.png" alt="" width="88" height="59" />

Voice

Record and Play Voice Messages; Using standard Windows equipment

<img style="display: block; margin-left: auto; margin-right: auto;" src="/images/Tech12.png" alt="" width="155" height="166" />

Terminal Server Connection (minimum requirement)


1. 1024x768@16 bit color: ca. 30 Kbps per session*
2. Each increase in screen resolution or color depth requires about
    3-4 Kbps more bandwidth per session
3. RAM: 100 MB per session

<img src="/images/SternchenZusatz.png" alt="" width="756" height="352" />

 

 

<tbody> </tbody>

<a style="font-size: small;" href="/index.php?title=Main_Page">Back to MedITEX products</a>

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