The project of corporate Hospital Information System (HIS) implementation is carried out using the Medotrade project implementation methodology, developed on the basis of successful executions of 60 projects on healthcare institutions automation. This section contains descriptive information concerning used implementation methodology: project stages, stages goals and tasks, work results, stages output documents. This section does not contain account men and performance time data.
The project stages include:
• Project management;
• Software presetting;
• Training and solution setting;
• System startup and initial maintenance.
By every stage completion summary reports, testing reports, record sheets, instructions and other documents are provided.
Stage 1. Project Management
This is a preliminary stage. In the course of the stage preparatory works are carried out for the starting of project works.
During the stage the following works are carried out:
• organizational preparation of the automation object for implementation;
• working-out and matching of the Project Management Plan;
• providing the departments of the automation object with Guidelines and Procedures;
• designating persons in charge of implementation on the part of the Customer by healthcare institution order;
• preparation of project infrastructure (rooms and equipment) for Executor implementation group;
• installation and Customer’s inspection of hardware and software support for project execution according to the Executor’s requirements (server, network neighborhood, personal computers, software, server remote access);
• data analysis and preparation from the systems in operation (if there are ones) for loading into the HIS.

The stage results in the following documents:
• Customer’s Order on Work Start and Designation of Persons in Charge (Project Management, Chief Technical Officer, System Administrator, Key Users) in healthcare institutions;
• Approved Project Management Plan;
• Letter of Notification from the Customer about hardware and software support readiness for project execution;
• Protocol of Passing Regulating Reference Data concerning Healthcare Institution.

Stage 2. Software Presetting
During the Software Presetting stage one initially customizes the solution according to the requirements list and the documents received by preliminary inspection.
During the stage the following works are carried out:
• system parameter setting by the Executor;
• system classifier setting;
• testing of made settings;
• developing of end user documentation;
• remote installation of the solution on the Executor’s server;
• installation of the client software on end users’ computers;
• matching Plan and Schedule of customer’s persons in charge training;
• preparation of lecture rooms and equipment by the customer (projector and clients’ workstations) for training conduction;
• passing of Guidelines and Procedures to the Customer for the staff’s self-preparation by use of educational materials previously given out;
• developing and matching of Software Testing Procedures.
The stage results in the following documents:
• Register of Settings Made;
• User Work Manuals according to requirements list;
• Letter of Notification about the Customer’s execution of works on software installation on the clients’ computers;
• Letter of Notification about  the Customer’s execution of works on preparation for training conduction;
• Approved by the Customer Plan and Schedule of training of persons in charge;
• Approved by the Customer Software Testing Procedures.

Stage 3. Training and Solution Setting.
In this stage the persons in charge are instructed about working with system functionality; one defines and carries out ultimate requirements list for workstations setting; besides, one takes suggestions for further system development.
During the stage the following works are carried out:
1.  As for training:
• the Executor conducts lectures for key users;
• the Executor conducts group workshops for key users;
• the Executor trains IT-department personnel of automation object for system administration skills;
• the Customer’s key users train end users;
• the Executor assess the customer’s staff through a test, according to the test results the users are authorized to work with HIS.
2.  As for software setting
• the Executor corrects User Work Manuals (if necessary);
• the Executor makes additional workstations settings according to detected peculiarities of customer’s business processes;
• joint system testing according to approved Software Testing Procedures.

The stage results in the following documents:
• Training Record;
• List of Notes and Suggestions fixed;
• Execution History of realized notes in additional workstations configuration;
• Customer’s Order of appointing the Committee for solution testing;
• Software Testing Record Sheet;
• Record Sheet of the discrepancies in relation to testing results;
• Customer’s System Startup Order.
Stage 4. System Startup and Initial Maintenance
In this stage one system running is started up and initial maintenance is provided.
During the stage the following works are carried out:
• the Executor consult remotely the Customer’s persons in charge of support concerning system operating;
• the Executor corrects mistakes detected by the Customer’s by working;
• the Executor takes suggestions for further system development.
The stage results in the following documents
• List of Requests Processed and Errors Corrected;
• List of Fixed Suggestions;
• Work Done Certificate under the Contract. 
Risk Management

Project risk is an event or a condition which by emerging can positively or negatively influence one of project goals, for example, timeframe, costs, contents and quality.
Overall responsibility is born by a Customer’s Project Manager who should discuss the risk with an Executor’s Project Manager after receiving relevant information (involving necessary project team employees if necessary).
The Executor’s Project Manager is responsible for operating supervision of risk management process.
Below you can see joint risk management and minimization strategy.

1. Prompt decision-making: during the project it could be necessary to make organizational, technological and methodological decision on a tight schedule.
2. Efficient allocation of necessary resources: the representatives of the Customer’s department automated are permanently included into the project groups, the key users are involved by project decisions making and system testing.
3. Methodology knowledge: the Executor’s methodology is used by project execution. One of the main Customer’s Project Manager’s duties is to use this methodology and to teach this methodology to the Customer’s staff.

Project risks decreasing factors.

1. The Customer’s management should contribute to successful project execution as well as solve efficiently emerged problems which can influence implementation course and project scope.

2. The Customer’s project group should have enough time know the project significance for the project to be successfully executed. Project group key members are to work on a full-time basis.

3. The Customer is responsible for operational management of changes in institution business-processes by project execution.
4. Healthcare Institution Manager supports the project constantly and takes interest in efficient project course to ensure exact and timely decision-making process.
Meeting the conditions one can minimize risks and reduce time for every stage of HIS implementation in a healthcare institution.