Consultant Perspective: An Inside Look at a Healthcare IT Consulting Project

Posted by Joann Hoxha on Jul 9, 2015 12:00:00 PM

Find me on:

Ever wanted an inside peek at what a day in the life of a healthcare IT consultant is like? One of our healthcare IT consultants was kind enough to keep a log of one of her projects. Here's what the project entailed: 

An Oxford Healthcare IT client had a critical need for a Meditech Client Server ORM documentation only install, with an aggressive deadline of just three months.

The client had an incomplete build of ORM that was still on paper. The intra-op build had not been started, and the documentation build had not commenced.  The client needed a strong ground-up builder who was an RN with multiple ORM implementation experiences. An RN would be the ideal candidate to pull along clinicians who were pushing back on the initiative. In addition to simply having experience, the client needed someone who was a cultural fit to ensure the success of the project.

Oxford Healthcare IT matched the client with a healthcare IT consultant who not only had the necessary Meditech ORM skills and expertise, but was also an RN. Her acumen of professionalism, experience with clinicians, and diplomacy would be key to establish buy-in from the start, and keep the project on track.

Weeks 1-3: Establishing rapport

The consultant quickly got to work, meeting with all members of the team, and reassuring all departments that the build would reflect their needs to every extent possible.

She then met with all representatives from the Perioperative departments, shooting for one-on-one meetings at every opportunity to make the process less confusing for all parties involved, and allowing for users to privately share any concerns they might have.  

Weeks 4-6: Confirming requirements with the client

Next, it was time for the consultant to review all data that was built previously. Certain data was obsolete, so the consultant had to be familiar with all of the language in the ORM dictionaries to ensure a solid foundation on which to build.


In this case, the desire was to build PCS Nursing Assessments; versus CDS (Customer Defined Screens).  The consultant explored and detailed the requirements driving the utilization of Nursing Assessments that were either already present in PCS or building new; which in turn sends the OR information to the EMR.  From there, the consultant outlined the key benefits and challenges of each approach.

Weeks 6-8: Establishiing the mechanism of documenting medications

The consultant considered the pros and cons of products such as Pyxis/Omnicell versus a stand-alone medication dictionary. Requirements are greatly dependent on the facility and the use of an automated form of dispensing medications. Like any requirement, there were advantages to either approach, so an evaluation of what was available and what product was in the client’s long-term application or hardware plan had to be assessed.

Weeks 9-12: Project progression and documentation

These final weeks were essentially a “dress rehearsal” before the go-live date. The consultant prepared for a parallel run as though it was a complete build, scheduled end user training, and stayed involved until the assignment end.  

The consultant used paper documents as a guide for building documentation, and made the electronic documentation look as much like the paper version as she could, which the client appreciated, since it mimicked the present flow of their documentation and, as a result, was more intuitive for the users.

The final result: 

The client was overjoyed with the results of their MEDITECH ORM documentation install.

Want to learn more about the secret to our consultant's success on this project? Download our whitepaper on EMR implementation today!

EMR implementation guide

Topics: Healthcare IT