Which Parts of an EHR Implementation Should Be Their Own Project?

Posted on September 29, 2014 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 10 blogs containing over 8000 articles with John having written over 4000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 16 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of InfluentialNetworks.com and Physia.com. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.

A really great discussion has been started on this post about staged patient portal implementations. Here’s one comment that really struck a chord with me:

I think that on a lot of strategic roadmaps “patient portal” is listed as a goal…a one time deadline without understanding how the patient portal works; what information flows into a fully functioning portal and to the patient; and what the system, risk, and security requirements are to consider.

This will require C level suite and decision makers to ask questions that might be getting them “into the weeds” a bit or questions that they may not know to ask. This is why a several strong consultants that are specialists in individual subject matter might be needed – instead of one project manager expected to move the project plan forward on the road map and to know everything.

This comment is right that the patient portal is often seen as a line item on a project plan that just needs to be completed. That couldn’t be farther from the truth. As one person said, sometimes you can get a grand slam, but most of the time you have to do a bunch of little things along the way. A patient portal is a great example of this. You don’t just implement a patient portal one time and then it will run forever. There’s more you can do to leverage a patient portal for your institution.

Are there other parts of an EHR implementation that exhibit similar characteristics? Maybe you implement them, but there’s always more that could be done to improve its use in your organization? Templates and workflow are one that come to mind. There should be an ongoing evaluation of your templates and workflow in order to ensure that it’s as optimized as possible.

What other pieces of your EHR project could benefit from a separate staged project plan? Of course, this assumes you’re starting to think more strategically than just trying to check off the MU check boxes.