Project implementation of the software

I am doing the project of medical software now. When looking for a job, nen do not know what to do, the Internet search, the implementation of the project has very little information. I will share with you here.

Our company is to do electronic patient record software. I came in as an implementing engineer. Now is engaged in a city medical group's electronic medical Record project implementation. The boss and I are in charge of this side of the business.

Just come here, eldest brother to hospital and two other manufacturers to talk about interface, of course, our company also sent developers to talk. In this group, there are three manufacturers at this stage to implement the project, there is a factory is his, did 10 years, after many times. There is also a factory is IBM. It is a platform for the group to use a variety of software integrated on their platform, with their platform to log in. The other is our company. Our company is here to make an electronic medical record. Including the basic writing of medical records, the writing of Nursing Records, the writing of orders, the rational use of drugs and quality control. Our software will not only read the patient's information from his, but also send his information to IBM's platform. So the interface of three software must be settled. The interface thing is the boss and the company's developers to talk about. This is the first step in the implementation of our project.

With the exception of the interface, the first thing the boss and I did was build a database. The group requires that we use the Linux system. And with the latest Linux CentOS6. The system came out only this year. There are not many people to use. So there is less information on the Internet. Although the company has installed documents, but also tested installed, but we are in the hospital this side of the installation process, or a variety of problems. The boss and I took one weeks to install Oracle 10g under Linux CentOS6.

The second thing is to install the application server under Windows. Just install the IIS service, configure the good things on the line. This is not difficult.

When these are settled. We need to test the use of our electronic medical records. In the hospital training room, we built the test environment. This is for testing and training purposes.

After that, things are trivial.

In electronic medical records, it involves templates and forms. Template is the format of hospital medical records, this is very important, must be determined. The form is the hospital nurses usually use various lists. Includes a variety of assessment orders, record sheets. In our electronic medical records, templates and forms also have, but each hospital has its own specific format, so we have to determine the template and form, according to the hospital requirements. I believe this step is common in the implementation of software projects.

You must make some changes to your software according to your customer's needs. The implementation engineer is the one who makes these changes. According to the software architecture, some software implementation personnel to modify the source code; Our company does not need. All you have to do is make those templates and forms. Behind the code you don't care. This software architecture has saved many things for the implementation staff.

While we are making templates and forms, we also determine the arrangements for the entire implementation project. The hospital Information Centre also has a training programme. This training program involves every medical staff. In the implementation of our electronic medical records, training is also a very important piece of content. Training includes training for the information centre personnel, including training for doctors, as well as for nurses. Each piece of training content and requirements are different.

After the training, is the electronic medical record software official on-line. At this time the official library and the official server are all set up. The client has been installed as well. Early preparation is good. is officially online. This is the most problematic time to test you. There must be something that you do that doesn't meet the needs of the hospital. It's either doing something that doesn't take into account special circumstances. In the early days of the problem, you have to do overtime to change things, you have to communicate with the medical and nursing Department of the hospital, you can not Shine them, but also can not ignore their requirements. You have to communicate. It is up to you to communicate what you can, what you can't, what you do now, and which you can put aside.

After the early problems have been dealt with, our work will be relaxed. Basic is some maintenance work. There are fewer problems, but there must be some small problems with the doctors and nurses themselves to manipulate the problem ah, we do something. At this point, we just need to do some maintenance on the line.

That's what I'm doing now. Sum it up. The first step is to talk about the interface (the project leader and the company's developer); The second step is to submit the project Progress Book (the hospital is sure to, the project owner to write);

Build test database server (this is very important); The fourth step is to build Application server and test environment, fifth step, test use, sixth step, training in test environment; seventh, set up official database server, formal application server and installed client; Eighth step, use at the beginning, Frequent problems, problem solving, communication and communication; The tenth step, after the initial period, enters the maintenance period.

Some projects you can import the formal data into the test library, direct test modification. Wait for no problem, just online use. But in doing so, you have to consider the progress of your project. Problems are discovered in the course of use.