Implementing an electronic health record (EHR) can be a difficult task to take on and planning the process is of utmost importance to minimize errors. Evaluating the selection criteria and implementation plan of an EHR system, intending interoperability, confidentiality, availability, and integrity of the patient health information data, while ensuring timely, accurate, and regulatory compliant generation of reports is a critical task.
This article discusses the selection and implementation plan that will primarily consist of assessing existing institutional workflows for each department, and it outlines the necessities and inclinations of the institution to include in the EHR system for the organization to function properly. Resources and tools are included to assist in the selection of the product as well as ideas on how to train staff and evaluate staff readiness. Regulatory requirements are also included for consideration during the initial process.
EHR increases the logistic productivity of workflows and offers a safer way to care for patients. To ensure efficiency, there is a series of steps the provider’s staff must follow to ensure proper implementation and handling of the EHR system. Before using the implemented EHR, it is recommended to have a testing protocol in place to ensure areas of possible staff confusion are identified and controlled. Using a proper implementation strategy for a new EHR system can facilitate success, minimize delays, and increase health care worker’s satisfaction and decrease the chances of usability being compromised.
Introduction & Background
While searching the internet for literature related to the selection and implementing of electronic health record (EHR) systems, it was observed that several publications were addressing a specific aspect or a few aspects of the selection and implementation. However, there were very minimal to no publications that include most, if not all of the required aspects from selection, regulatory, to implementation and post-implementation of the EHR system in one source. The authors list a series of recommendations and tools for use. All of these tools to facilitate the successful EHR system implementation process are in one single source.
EHR Implementation: resources and tools
Implementation of EHR systems has become a requirement in the United States. The Centers for Medicare and Medicaid Services (CMS) have lead this transition with financial incentives for healthcare providers and healthcare organizations, name "providers" in this paper. However, not implementing the EHR will bring financial penalties for non-compliance. Many providers have been using a legacy (current/old) system as an EHR. The EHRs are mostly hybrid and some providers have service-lines or departments with computers that do not have an informatics system build for their use. Neither they have systems that can interoperate with the computers from the rest of the organization; an example can be the pharmacy or laboratory departments.
Some providers may have certain departments with an informatics system integrated such as the lab or billing, but the reporting capabilities are not sufficient to meet the needs of the business and the accreditation requirements and thus reports are manually created. For these clinical and administrative healthcare informatics problems, providers give priority to the implementation of a certified EHR and allocate a budget for the acquisition and adoption of the healthcare informatics system: EHR.
The legacy EHR may meet some of the CMS Meaningful Use requirements but may not be fully ready to meet stage three of the meaningful use requirement. The areas needed for the legacy system to be fully compliant are for the EHR to be able to generate and transmit discharge prescriptions and provide patients with electronic access to their EHR .
In learning about certified EHR options, one has to also consider the cost of the implementation and adoption. Some healthcare workers will be pulled out from their daily responsibilities to attend to the needs of the change through EHR implementation. In searching for certified EHRs, the organization looked at these categories to evaluate the new system the usability, functionality, utility, and cost. The usability and functionality category were selected to test different routes of access while documenting and characterizing representations of specific data required for information. Utility was selected because the organization needed to evaluate how accurately and completely the health record will present diagnostic and therapeutic information .
At a 260 bed hospital, the selected EHR certified product  for evaluation was Medhost EHRs; Cerner  was also considered. MEDHost Enterprise 2019 consolidates clinical, electronic prescription, patient education, and financials in one product . The key features evaluated on MedHost were the computerized provider order entry (CPOE) system, clinical decision support system (CDSS), drug-drug allergy interaction checks, patient-specific education resources, data portability, authentication, access, control, and authorization among others.
The selected EHR met most of the specifications per criteria selected by the hospital and was the most economical software and still met the requirements. The implementation of the new EHR, will mitigate patient safety events from occurring such as medication errors due to pulling the wrong medication for a patient, minimization of risk of loss of patient health information due to the security systems that will be implemented such as specific user access to information per employee role and username and password, and compliance with HIPAA rules and accrediting and licensure agencies. Also, it will provide patients access to their health information, which meets meaningful use criteria.
The implementation process will first consist of performing an evaluation of the current organization’ s workflows for every department in two to three days, define the needs and preferences of the organization to have in the EHR for the hospital to function planned into one to three months, including hardware needs, deployment of selection and training of super users, to take about one week, and then plan the implementation and staff education to go live in about one more month. The plan for complete implementation roll out from go-live day to full adoption will be between six and eight months.
Testing the EHR
Testing the implemented EHR ensures that every system in place is put through its paces to ensure data tables and files are loading properly, data collected are processed and store correctly. In addition, it ensures that the system interfaces work as intended, that the workflows have been adjusted appropriately, that alerts are properly triggered and responding correctly, that the reports are generated accurately and completely and that the security system is also checked to ensure it is correct.
This paper offers a list of objectives for the test, set a scope of the test, establishing a testing strategy, establishing the environment requirements, create a test schedule, establishing a control procedure, identify functions that will be tested, creating a list of deliverables, and identifying risks.
Testing scope and environment required
In preparation for testing, the scope of the test will be defined as the testing for infrastructural readiness, application configuration readiness, and training readiness. These testing will include the evaluation of workstations, printers, servers, and wireless devices and related security measures. This part of the plan will include testing all workflows, procedures, and areas of the clinical record design. Training will also be included in this part of the testing to evaluate staff readiness in the use of the system before “go-live.”
The testing will be performed using a testing environment with actual patient data but on a separate section of the database that is not in production. Wright, Aaron, and Sittig  recommended to also test the system in a production environment for the system to mimic how it will behave when the system is live. After the system goes live, an ongoing regression testing assists in identifying that the system has not created new issues and that any new problems are identified and addressed.
Objectives for the test
Developing testing objectives such as the ones listed herein will help ensure that the system is working properly and producing the correct results. One of the objectives of the testing is to test the unit and functionality. This testing ensures that the major functions perform as required, that the customizations work as requested, that the screens appear as intended and screen functions properly, that there are no spelling errors, and that the content is appropriate. A second objective is to test the system to ensure that workflows send and receive data properly between the systems, that the interfaces between applications move data correctly and completely, that users gain access per assigned privileges, and that the data are processed accurately, in graphs, stables, claims, summaries, and it populates correct data in registries, reporting warehouses, etc.
The third objective will be testing the integrated system to ensure all system components work together, ensure workflows reflect the processes and workflows of the organization, that it follows policy and procedures, and that the system works with all mobile devices and with all of the devices and system capabilities such as voice recognition and speech commands, etc. The fourth objective will be to test for performance and stress to ensure response times process interactions within the system timely and within acceptable limits, evaluate system usage peak loads for accessibility and timely process of requested data, and timely generation of reports and evaluation of time for data dumps on system performance.
Testing strategy and test schedule
The strategy to test the system includes a pre and post-go-live system testing, a patient communication guideline to include expected downtime, staff scheduling and required overtime or temporary staff, modification of appointments and scheduling, reporting processes for system and project evaluation, communication tools (boards, etc.), network speed and reliability checks, and data backup processes. The purpose of performing testing is to ensure the system works and performs as expected [7-8].
During system testing, one needs to ensure that the team conducts unit testing (i.e., single module), conducts integration testing (i.e., interaction between two or more modules), conducts interface testing (i.e., interaction between systems), conduct system stress or load testing, ensures testing plans cover different scenarios and situations, contingency planning by developing a disaster recovery plan, testing the ability to restore system from backups prior to go-live, ensuring that the system backup plan in place and running and arrange for regularly scheduled pick up and off-site storage of backups . During testing, day one will begin with testing for data availability to ensure that data is accessible and usable upon demand by authorized individuals, test for data quality and integrity to ensure the data and information is accurate and created appropriately and have not been altered or destroyed in an unauthorized manner, test for data confidentiality to ensure data and information is only available and disclosed to authorized users and processes, during testing day two, testing will be to test for complete and correct electronic health record use to ensure its features and functionality are implemented and used as intended, and will also test for system usability to ensure its features and functionality are designed and implemented so that it can be used effectively, efficiently, and to the satisfaction of the user. During testing day three will test again to monitor and improve patient safety to ensure that an ongoing quality assurance and performance improvement mechanisms are in place to monitor, detect, and report on the safety and safe use of electronic health records .
The risks associated with the testing and implementation of the new EHR system are those related to not achieving the objectives set for the EHR implementation. Having data that is incomplete, missing or misleading, open or incomplete patient orders, procedures and policies that are ineffective, failure to follow up abnormal test results, confusing one patient with another, reliance upon inaccurate or incomplete patient data, intentionally or accidentally subverting Clinical Decision Systems (CDS), automatic discontinuation of a prescription, data aggregation leading to erroneous data reporting, and prolonged EHR downtime among other legal related mandate risks.
Functions that will be tested, list of deliverables, and control procedures
The testing plan checklist from Health IT in Table 1  below, is a great tool to use to ensure functions and components are tested, identify all deliverables, and to control all items to be identified and addressed with documented findings and plans to solve issues.
The EHR roll out
The strategy to roll out an electronic health record will be that of planning each step of the execution of the project until go-live and after by monitoring and controlling the effectiveness of the system. It is important to consider each step of the execution to ensure a smooth transition of the system and increase staff satisfaction with the use of the system for usability purposes. To implement the EHR, the implementation team must consider the approach to the implementation and the strategy of the implementation.
There are two different types of approaches to launching the electronic health record the Immediate Approach and the Incremental Approach. The Immediate Approach has the advantage of minimizing the time spent managing both a paper record and the new electronic system simultaneously, it can be disruptive and small system glitches can be amplified  The Incremental Approach has two different formats, one is by turning on certain functions in a step-wise approach and the other is by implementing the EHR in certain sites or departments and slowly roll out to the rest of the organization, learning and tweaking the process along the way; Table 2 below shows the different implementation approaches that can be used (Hodgkins, 2015) .
Upon the decision of the launching approach, the implementation strategy can then be considered based on the approach. Table 3 below shows the different implementation strategies that can be used based on the approach (Hodgkins, 2015) .
Implementation strategy: identification and selection
Based on the identified approach and strategies for electronic health record implementation presented, the implementation team has decided to use the incremental approach and strategy to improve physician and staff satisfaction, identify and gaps or system glitches that can appear and have the opportunity to correct them before full implementation, and reduce productivity loss due to implementation. If on the other hand, the team should have decided to use the Immediate approach, there was a consensus within the implementation team that the staff and physicians may not be satisfied with the EHR and thus usability will be compromised as well as decrease in productivity due to all staff expending time on learning and running into system issues and possibly delaying the implementation and proper use of the electronic system.
When all implementation has been completed and the EHR system begins to be used, the question that remains to be answered is that of what will happen if the system fails for any reason, including not having electrical power. A recovery plan will be recommended to be considered and be in place to ensure that there is continuity of the service even though the electronic health record may not be available. Recommendations [8,13-15] to consider ensuring the purchased EHR system includes all necessary hardware, software, and utilities to support system back-up and recovery processes. Ensure that the system includes “redundant processors that contain copies of data files from the active EHR system to be quickly switched to the redundant system to continue operations” .
The recovery and back-up plan of the EHR is not only a best practice to include in the implementation of the new system, but it is a requirement. The Health Insurance Portability and Accountability Act (HIPAA) mandates for providers to back-up their electronic health record system and have a plan in place in case it fails. The elements that the HIPAA rule has mandated to incorporate to ensure that electronic protected health information (PHI) is secured in case of emergencies or disasters are data back-up plan, disaster recovery plan, emergency mode operation plan, testing and revision of procedures, and applications and data criticality analysis [8,16-17]. Table 4 shows the recommended processes to consider having a back-up plan in place (Code of Federal Regulations, 2007; Contingency planning, 2011; O’Dowd, 2018; Sahi, Lai, & Li, 2016; Tate, 2015; U.S. Department of Health & Human Services. 2013) [8,14-17].
A recommendation for training is to complete a user skills assessment and training needs before implementation. A user skills assessment evaluates the healthcare worker’s basic computer literacy and skills. This assessment could be considered as a competency demonstration and training can be provided as needed. There are many healthcare workers that a highly proficient in the use of technology such as computers, however, there is segment of the healthcare workforce that may need basic computer training such as how to use the mouse, navigate on a screen with the use of a scroll up and down, identification of tools, etc. The skills assessment is to be done before implementation to ensure skills are build up and ready by the time go-live happens.
The training strategy can be that of selecting super-users per each of the Health Information Systems such as Billing, Quality, CPOE, Nursing, etc. Super-user training should be considered to be happening before implementation to become familiarize with the system, feel comfortable teaching their part of the system, and in case the selected staff prefers not to be included. Consideration of having two super-users per health information system be trained is recommended in case the primary super-user goes on vacation or leaves the organization, this way there is always someone trained available to staff. The training approach could be that of a peer-to-peer approach as it facilitates training as peers communicate and speak the same language of the people they are training. Other teaching methods can also be included at the same time such as classroom-based training, e-learning modules, hands-on learning methods, one-on-one, and training staff only on the EHR areas they are going to use to avoid confusion and expedite the training and implementation .
Training should be considered to be performed throughout implementation and after go-live to ensure users feel competent and comfortable with the use of the new EHR system. Training session length times may vary from 1 hour to 8 hours especially for physicians who may need longer times. Training for staff should be considered to begin 2-3 weeks before implementation and go-live for basic skills and then classroom sessions, followed by e-learning, hands-on, and one-on-one training at different days and times of the day. Re-training should continue for optimization after go-live for 6 to 10 weeks. After the 10 weeks, re-assessment status should be done to evaluate the need for more training.
EHRs not only provide a means of organizational efficiency but provide a safer way to care for patients and the required means to meet regulatory standards. The implementation process is an important step to consider when adopting an EHR in healthcare organizations. Selecting and including the appropriate strategy can facilitate success and minimize delays in the system rollout. Becoming familiarized with the approach and understanding the needs of the organization are detrimental steps to the success of the implementation. Using the best approach, strategy, back-up system and training increases healthcare worker’s satisfaction and exponentially decreases the chance of usability been compromised.
- Medicare eligible hospitals, critical access hospitals and dual-eligible hospitals promoting interoperability program stage 3 objectives and measures for 2018. (2018). Accessed: July 1, 2019: https://www.cms.gov/Regulations-and-Guidance/Legislation/EHRIncentivePrograms/Downloads/TableofContents_EH_Medicare_S....
- Kim MI, Johnson KB: Personal health records: evaluation of functionality and utility. J Am Med Inform Assoc. 2002, 9:171-80. 10.1197/jamia.M0978
- API information for 2015 edition products. (2015). Accessed: July 1, 2019: https://chpl.healthit.gov/#/collections/api-documentation.
- CEHRT disclosure information. (2015). Accessed: July 1, 2019: https://www.cerner.com/cehrt-disclosure-information.
- Medhost: regulatory and compliance. (2015). Accessed: July 1, 2019: https://www.medhost.com/who-we-are/regulatory-and-compliance/.
- Wright A, Aaron S, Sittig DF: Testing electronic health records in the "production" environment: an essential step in the journey to a safe and effective health care system. J Am Med Inform Assoc. 2017, 24:188-192. 10.1093/jamia/ocw039
- EHR implementation plan: your 8-step checklist. (2017). Accessed: July 1, 2019: https://www.ehrinpractice.com/ehr-implementation-plan.html.
- O'Dowd E: Planning for data backup, recovery in health IT infrastructure. Hit Infrastructure. 2018, Accessed: August 1, 2019: https://hitinfrastructure.com/features/planning-for-data-backup-recovery-in-health-it-infrastructure.
- EHR implementation checklist. (2006). Accessed: July 1, 2019: https://healthit.ahrq.gov/sites/default/files/docs/workflowtoolkit/ehr_implementation_checklist.pdf.
- Green J: Using automated testing solutions during EHR implementation. EHR in practice. 2018, Accessed: August 1, 2019: http://www.ehrinpractice.com/automated-testing-ehr-implementation.html.
- The National Learning Consortium (NLC): Electronic health record (EHR) system testing plan. Health IT. 2012,
- Hodgkins M: Electronic health record EHR implementation: easy transition from paper to electronic health records. AMA. 2015,
- Outlook Associates: Contingency planning for Electronic Health Record systems. 2011, Accessed: Aigust 1, 2019: http://cshca-wpengine.netdna-ssl.com/wp-content/uploads/2011/06/6-Contingency-Planning-Tips-for-Success.pdf.
- Sahi A, Lai D, Li Y: Security and privacy preserving approaches in the eHealth clouds with disaster recovery plan. Comput Biol Med. 2016, 78:1-8. 10.1016/j.compbiomed.2016.09.003
- Tate A: Do you have a backup plan for EHR failure?. Becker's Healthcare. 2015,
- Code of Federal Regulations. (2007). Accessed: August 1, 2019: https://www.govinfo.gov/content/pkg/CFR-2007-title45-vol1/pdf/CFR-2007-title45-vol1.pdf.
- Summary of the HIPAA Privacy Rule. (2013). Accessed: August 1, 2019: https://www.hhs.gov/hipaa/for-professionals/privacy/laws-regulations/index.html.
- Mcalearney AS, Robbins J, Kowalczyk N, Chisolm DJ, Song PH: The role of cognitive and learning theories in supporting successful EHR system implementation training: a qualitative study. Med Care Res Rev. 2012, 69:294-315. 10.1177/1077558711436348
Electronic Health Record Implementation: A Review of Resources and Tools
Ethics Statement and Conflict of Interest Disclosures
Conflicts of interest: In compliance with the ICMJE uniform disclosure form, all authors declare the following: Payment/services info: All authors have declared that no financial support was received from any organization for the submitted work. Financial relationships: All authors have declared that they have no financial relationships at present or within the previous three years with any organizations that might have an interest in the submitted work. Other relationships: All authors have declared that there are no other relationships or activities that could appear to have influenced the submitted work.
Cite this article as:
Aguirre R R, Suarez O, Fuentes M, et al. (September 13, 2019) Electronic Health Record Implementation: A Review of Resources and Tools. Cureus 11(9): e5649. doi:10.7759/cureus.5649
Received by Cureus: August 26, 2019
Peer review began: September 01, 2019
Peer review concluded: September 06, 2019
Published: September 13, 2019
© Copyright 2019
Aguirre et al. This is an open access article distributed under the terms of the Creative Commons Attribution License CC-BY 3.0., which permits unrestricted use, distribution, and reproduction in any medium, provided the original author and source are credited.
This is an open access article distributed under the terms of the Creative Commons Attribution License, which permits unrestricted use, distribution, and reproduction in any medium, provided the original author and source are credited.