CPOE has numerous advantages and this is the reason that all the major hospitals are switching their order systems to CPOE. Although this whole transition from paper recording to computerized recording system of orders is very lengthy and time-consuming. Everything seems to be quite easy but when you will start implementing it, you will realize the real problems in this transition.

CPOE is a very expensive system and if you don’t have a lot of capital, you cannot implement CPOE. Since it’s a whole system that is not only related to the order entry system rather it is a bridge between all the departments of a hospital. The records of all the patients are maintained properly and can be accessed by everyone (authorized individuals only). So it’s a very costly project to introduce CPOE in any hospital. Besides, implementation of a computerized physician order entry system can take years and importantly, those who will be using the system need to be trained which is another hectic as well as time-consuming activity.

But a computerized physician order entry system has many benefits both for patients and for medical staff members. CPOE has made the life of clerical and medical staff members quite easy, on the other hand, patients now have everything written and recorded and they don’t need to maintain their own records or to remember everything. Everyone loves to have everything properly managed and organized, and CPOE does exactly that. It is providing patients with extreme safety and hospital management and physicians are finding this system quite useful. All in all, a computerized prescriber order entry system is a patient oriented system.

Story goes back to 2012, when we were maintaining three small websites through Host Guy. We met Host Guy at a party, the good friend of a good friend, and he was friendly, laid back, and apparently technically savvy. Apparently.

Understand that the “we” writing this story is actually just one word processing professional who was a beginner at site development and very dependent on WordPress and Host Guy. We were maintaining three WordPress blogs: A personal web journal, a TV fan site, and a movie discussion site. None of which were setting the world on fire. Host Guy helped with design issues, tied legacy HTML to the WordPress blogs, and charged very little. Faced with several WordPress backup options, we asked his advice. “I don’t see why you should bother,” he said, “I do a nightly backup.” We believed him.

Please, I beg you, do not believe this. This is not a thing to believe! The backup of the entire WordPress file structure as it exists in the File Manager in CPanel has no data. Presumably our readers are knowledgeable and already know this. We did not. We’d been blogging along for a few years, not understanding the difference between “wpcontent” and the WordPress database. So let’s spell it out very clearly:

1. All of your posts, all of your pages, all of your images, and all of your comments, are in the WordPress database.
2. A routine server backup that copies all files in the CPanel does not backup the database.

You can probably see where this is leading. Host Guy’s advice on backups was dead wrong, and a catastrophic server class taught us this tragic lesson. The folder called “wpcontent” is, perhaps, misleading: It doesn’t contain any “content” as a site owner is likely to understand it. There are no posts, pages, or pictures saved in “wpcontent.” The databases of these sites, which were several years old, had never been backed up.

Let our tragedy by your wisdom.