Define and Validate Workflows
Application workflows are a valuable tool used for system validation, determining application build requirements and confirming build match specifications. They can also be used during training and go-live support. Integrated workflows provide an opportunity to see how the applications integrate across the organization and establish a great foundation for integrated test scripts and testing requirements. Be sure to validate workflows early on and consider multiple patient scenarios.
Allocate Resources Early On
Testing occurs at a very busy and critical point in implementation. Accurate and in-depth testing requires the participation of multiple resources across the organization. Preparing and allocating time and resources and a dedicated testing space should occur well in advance. Resources, including project team members, subject matter experts and key stakeholders for the project need to be engaged from the beginning of implementation planning, when the testing strategy is being developed, all the way through testing execution to provide the most value and continuity.
Develop Scripts Collaboratively
The time required to develop accurate and pertinent testing scripts is often underestimated. The most valuable test scripts come from a collaborative group of project team members and key operational staff. In particular, integrated test scripts require a collective group effort to ensure clinical and financial input into the test script are appropriate and meet the requirements of all the applications and operational departments involved. Integrated scripts developed in the silo of a project team often remain focused on functionality and may not reflect real world content. Script development refers not only to the traditional methods of creating a “paper” script but the development of automated test scripts utilizing test management tools. Either method requires adequate time to develop the final product.
Track Testing Process and Outcomes
Tracking the testing process from requirements to completion is essential. By tracking requirements upfront, you have a defined set of expectations to manage during testing. Monitor and track outcomes during each testing phase that correspond to the requirements, so you have a clear understanding of what needs to be tested, what was tested, when it was tested and if the test was successful. Every organization may define different criteria for success, but tracking the process is critical for determining whether or not criteria are met.
Preparing for and remaining mindful of testing during all the phases of an EHR implementation will help make it more effective and valuable. A testing strategy and plan that are well thought out and communicated will not leave the team wondering if the system has been thoroughly vetted. Incorporating test planning early and continuously, and adjusting throughout the project as needed will ensure more organized and successful testing outcomes. The value of your efforts—and your EHR—will be realized when you can demonstrate your testing was well planned and executed through a reduction in issues and unaccounted risks.
Original article appeared here.