Electronic health records (EHR) are transforming the way behavioral health organizations conduct their business. It's true that virtually any clinical or business process done using paper can be replicated electronically. And because, with an EHR, information can be accessed, analyzed and manipulated in ways more meaningful than previously possible, workers and managers can make smarter decisions and accomplish most day-to-day tasks much more efficiently.
However, while there are many advantages that come with the switch from paper to electronic systems, a successful EHR implementation requires serious planning, careful analysis and thoughtful attention to how staff will interact with the system. For these reasons, the early stage of an implementation project is a good time for a reality check with the organization's key stakeholders. A reality check requires an organization to acknowledge the challenges and issues it will encounter during and after the implementation of the EHR, which will in turn allow it to create a set of realistic expectations for the execution and outcome of the project.
There are basically two types of issues an organization will encounter with the implementation of an EHR: real issues and psychological issues. Real issues refer to functional items such as deciding which tasks the system will perform and how much time and effort the project will require. Psychological issues usually involve the resistance to change that staff members may experience as they transition into using the new system in their daily work routines. A reality check provides an opportunity to understand and prepare for these issues before they arise. Let's take a brief look at both of these issues, as well as a strategy for dealing with them.
Behavioral Healthcare invites information technology vendors, including members of the Software and Technology Vendors' Association (SATVA), to contribute to this department.
How much time and effort will be necessary for your EHR to become functional? The implementation of an EHR is fraught with hundreds of decisions over the course of many months. During the process known as discovery, the development team explores the organization's processes and data uses to determine its business requirements. Agency executives and implementation project managers must absorb a massive amount of knowledge to make informed decisions regarding the setup and use of their EHR. One of an agency's most important decisions is selecting a compatible vendor. Some agencies conduct more than a year of research, talking with vendors to find one with whom they “click” and feel can best identify and satisfy their business needs. The agency must also create an internal implementation team that will collaborate with the vendor in executing the project. Software, and potentially hardware, will be installed, configured and tested. Finally, users will be trained to do their old jobs using the new EHR.
An EHR changes how people work and usually requires some members of the organization to take on new roles and responsibilities. Many will find the changes and new responsibilities exciting, while others may struggle and resist them. It is common for at least some staff members to experience the stress and anxiety that often comes with changing one's work routine, especially those who are less technologically savvy.
While the start of the implementation process is an exciting time, it is important not to be too optimistic about the challenges that lie ahead. The larger the gap between expectations and reality, the more stress and frustration will arise during and after the implementation of the EHR. A reality check serves the important purpose of helping to minimize the gap by confronting the real and psychological issues in advance.
Many organizations consider time to be their most valuable resource. For this reason, a reality check begins by acknowledging that the implementation of an EHR is going to take time. Underestimating the amount of time it will take to implement the system is one of the most common sources of frustration for agencies. Most have limited familiarity with software development projects and are often surprised by the sizable investment of time required. Project steps often take longer than initially expected. Closely related to time is the amount of effort that will be required. The complexity of an agency's workflows and processes will have a direct impact on the amount of input that will be needed from various stakeholders. Be prepared for lots of meetings, conference calls, and emails.
The entire organization will be affected after the EHR is finally operational. While taking into account the many new improvements and benefits that will be possible, coping with the changes may be difficult for some members of the organization. Project managers should anticipate and prepare for the inevitable resistance, which will vary from person to person. Although the majority of the staff will usually be open to change, even enthusiastic employees will need a fair amount of guidance through the transition period. Transitioning to the new system will require a significant amount of learning and staff members will learn at different rates. Depending on the size of the organization, training users and providing ongoing support may add new duties to staff members' existing workloads, furthering stress and resistance.