At it Alone: 15 Tips to Keep In Mind when Implementing an EMR
One very important decision when considering an EMR implementation is whether or not to use a third party system integrator to run the project. The decision to use a system integrator can add as much as 20 percent to the overall implementation costs. I have been involved in leadership roles with a system integrator at a major academic medical center and "going alone" at a regional health care system. There are many benefits of using a system integrator under certain situation. One size does not fit all.
There are several factors that must be in place in order to have a successful "go alone" strategy. They include:
1. Strong C-Level management support engagement
2. Good employee engagement prior to the project implementation
3. A stable work force
4. A capable and experienced internal project director
5. Strong IT leadership and processes
6. A commitment to hire a mostly internal project team and pull them completely out of operations
7. A commitment to training
8. Tools for project management, status, testing and many others
9. A commitment to the vendors project methodology
10. Strong clinical engagement, participation and leadership
11. Ability to slow or freeze the pace of changes to the existing EMR and other applications services
12. A very strong infrastructure and Integration team
13. Testing resources and methodologies exist in the current organization
14. Ability to internally execute a change management plan
15. Governance should not be a new experience as many difficult decisions need to be made in the course of the project.
When selecting system integration vendor it is important to know and understand the experience level of that service
In thinking about my prior experience at the major academic medical center implementation, the above are success factors even when hiring a system integrator. The distinction is that many times the IT footprint at larger health systems in inherently more complex with many more customizations and a high degree of vertical integration.
When to bring in a system integrator:
• Decision making in the organization is decentralized
• Requirement for more complex workflows and order-sets compared to out-of-the-box
• There exists many different IT divisions in the organization
• Desire to optimize current applications (compared to soft and hard freezes)
• Systems are behind on upgrade schedules for applications that will be maintained
• Low capability maturity levels in IT service management
Other considerations that may merit a system integrator:
• Strength and experience of EMR vendor's implementation practice
• CIO and IT leadership stability (especially strength of CMIO)
• Low credibility or missing skill sets in IT
• Little to no governance for IT/Business related decision making
• Low consumer perception or perceived low credibility of IT support services
• Competitive staffing market where high turnover exists or has potential to disrupt the project
When selecting system integration vendor it is important to know and understand the experience level of that service. Validation of the experience is required. The vendor should agree to provide a list of people who will be on the project. It is important to understand if the vendor team will be involved in multiple projects or focused on your implementation. Juggling multiple healthcare implementations by the same team is a red flag. Expertise in bringing in experienced individual contributors is also important. Many times the speed in which the integrator can bring resources to bear allows the organization to cut off problems early.
When going alone, one of the major challenges is identifying trouble areas early and having the ability to mitigate issues, first with internal staff, then with contract services. When using contract services, we have experienced some hit and miss resources. Making sure contract vendors are willing and able to respond quickly to needs and concerns is paramount. A good knowledge turnover plan is important as disengaging with the system integrator is important after the project is complete.
Another really important action for independent implementation is periodic independent audits of the project. The report should go to key board members, C-level and experienced contributors. We have been lucky enough to have three CIOs and one CFO from other hospitals participate on this advisory committee.