Testing The Workflow Of Electronic Health Records Systems Discussion

Testing The Workflow Of Electronic Health Records Systems Discussion

The purpose of this assignment is to apply user testing to the created workflow for the identified case study need.

Read the “Integrated Case Study” resource, located in Class Resources, prior to beginning the assignment. In addition, refer to the instructor feedback you received on the Topic 5 assignment.

Write a 750-1,000-word test script that answers the following questions: Testing The Workflow Of Electronic Health Records Systems Discussion

ORDER A PLAGIARISM-FREE PAPER HERE

Who would be part of the user testing?
What are the elements to test?
What are the recommended steps used to perform acceptance testing, integration testing of new systems, and testing of system enhancements?
Describe any rules involved.
What is the action/outcome expected?
What would the recommended action plan be if testing does not work?
Cite at least two scholarly resources in your response.

Prepare this assignment according to the guidelines found in the APA Style Guide

Nursing Informatics: Benchmark – User Testing Script

Who would be part of the user testing?

The installation of a new EHR system for the merged Oncology North and Oncology South would impact five categories of users; physicians, nurses, billing office, receptionists, and government agencies. All these groups will be required for user testing. These individual users have different uses for the workflow systems but are interconnected. For example, while a receptionist would want to test how well the basic information for a patient is entered into the system, populates necessary charts, and transferred to the physician, a physician on their part would want to verify that the proposed system is able to effectively document the time spent on each patient and generation of electronic prescription Testing The Workflow Of Electronic Health Records Systems Discussion.

What are the elements to test?

In focusing on the key elements of testing the workflow of an EHR system, the base element of a new system that must be kept in mind is that the objective is functionality (Keshta & Odeh, 2021). In view of this, a handful of elements will be tested. The first element is health information and data. The users will need to be consistent that clinical data from patients can be collected, stored, and processed fast to generate results. The second element is result management. Fennelly et al. (2020) quipped that the workflow of the EHR should be tested for all users in the two wings to access present and past health records for the enhancement of oncology patients’ care. Order management is the third element that needs testing. Recognizing the high level of activity of the two facilities (Oncology North and Oncology South), nurses and other clinicians need to verify that the systems are able to store entered orders such as prescriptions and expeditiously enhance their execution and delivery. On this, it is important to ensure that the workflow does not duplicate and is faster than the existing system in place. Physicians, clinicians and the billing office need to test whether the decision support system for their individual needs is working. The decision support system according to Watson et al. (2019) use the volumes of data stored on the organization’s servers to offer insights for decision making Testing The Workflow Of Electronic Health Records Systems Discussion.

What are the recommended steps used to perform acceptance testing, integration testing of new systems, and testing of system enhancements?

The workflow/EHR acceptance testing takes a number of key steps. These are;

  1. Test resource allocation. These include time and manpower that has been closely involved in or understand the new proposed system
  2. Have a keen awareness of the individual components of the system and tests involved
  • Planning of the process and steps of testing. Each of the individual scenarios for all stakeholders and elements of the system is broken down into small milestones for independent testing
  1. The creation of an environment ideal for system testing. Huang et al. (2020) advocate for an environment away from the one where the production was done and involves the presence of mock databases and software to be installed for the system
  2. The fifth step involves the actual testing of the various components of the workflow and making documentation of arising issues. Keshta and Odeh (2021) mention that it is during this step that discrepancies observed between the actual performance and expected outcomes are recorded.
  3. The last step involves the iteration of the fifth step until the desired outcomes are achieved.

Describe any rules involved

Perhaps the most important feature of the proposed system for use in the merged organization is the need to abide by standards for an electronic health system as suggested and recommended by the Institute of Medicine Committee on Data Standards for Patient Safety (IOM)Testing The Workflow Of Electronic Health Records Systems Discussion.

 

What is the action/outcome expected?

The objective of the installation of a new EHR system is to improve performance by the various classes of users. According to Fennelly et al. (2020), an improved workflow in a healthcare organization is to provide better healthcare by identifying areas of patient care and determining ways in which they can be improved. Ideally, areas such as safety, the effectiveness of communication and care delivery, education, and efficiency are especially focused on and the core intention of a new system at Oncology North and Oncology South is to achieve all these.

What would the recommended action plan be if testing does not work?

In the event that the proposed new system fails to work, repeated reviews and remodeling should be done. At first, the same vendor should be used to save on time and resources as there is no one system that is a fit for all. Watson et al. (2019) stated that EHR systems are designed to serve a handful of healthcare organizations but factoring in the fact that all organizations have their unique specialized needs, these systems are customizable. What this means is that the team installing the system into the merged organization cannot get it perfectly well the first time but needs to keep on trying until a time when all the user needs are met. Alternatively, if the testing fails to work even after multiple iterations, the healthcare organization could consider an alternative vendor that has more capabilities to create a system that serves their needs Testing The Workflow Of Electronic Health Records Systems Discussion.

References

Fennelly, O., Cunningham, C., Grogan, L., Cronin, H., O’Shea, C., Roche, M., … & O’Hare, N. (2020). Successfully implementing a national electronic health record: a rapid umbrella review. International Journal of Medical Informatics144, 104281. https://doi.org/10.1016/j.ijmedinf.2020.104281

Huang, S. C., Pareek, A., Seyyedi, S., Banerjee, I., & Lungren, M. P. (2020). Fusion of medical imaging and electronic health records using deep learning: a systematic review and implementation guidelines. NPJ digital medicine3(1), 1-9. https://doi.org/10.1038/s41746-020-00341-z

ORDER TODAY

Keshta, I., & Odeh, A. (2021). Security and privacy of electronic health records: Concerns and challenges. Egyptian Informatics Journal22(2), 177-183. https://doi.org/10.1016/j.eij.2020.07.003

Watson, J., Salisbury, C., Banks, J., Whiting, P., & Hamilton, W. (2019). Predictive value of inflammatory markers for cancer diagnosis in primary care: a prospective cohort study using electronic health records. British journal of cancer120(11), 1045-1051. https://doi.org/10.1038/s41416-019-0458-x Testing The Workflow Of Electronic Health Records Systems Discussion