Verified Document

Software Application Process Research Paper

Software Application Process for a Clinician Provider Order Entry (CPOE) system Software Application Process

Clinician Provider Order Entry (CPOE) System

The planning, customization, launch and continued use of a Clinician Provider Order Entry (CPOE) system in a local hospital forms the foundation of this analysis. The processes being used prior to the systems' planning and implementation are detailed to provide a basis of comparison of system contribution and performance. A timeline of the decision makers involved in the process, how and where they identified vulnerabilities in the system and the software selection process are also detailed. The CPOE system today on average handles over 10,000 queries and has resulted in a 78% reduction in order entry errors with a corresponding reduction in costs. Most importantly, it has drastically improved the healthcare providers' effectiveness in treating patients while also augmenting the entire patient experience more positively.

Analysis of CPOE Substitute Processes Prior To System Implementation

The series of processes and systems that had been in place prior to the CPOE system were manually based, required continual updates and manually recursive checks of accuracy. They also had very steep learning curves for those new employees, from nurses and healthcare providers to administrators to learn and use. The manually-based system had processes in place that were only oriented towards one department as well, and had to have more manually-based modifications to be used in advanced treatment areas incouding cardiology. On top of all these other factors, the manually-based CPOE system had manually-based approaches to filing for reimbursements and managing the more complex order entry and order management functions in conjunction with the leading insurance providers. Manually-based approaches to order management, transaction management and distributed order entry can cost a healthcare provider hours of administrative time and hundreds of thousands of dollars in error-field orders and misplaced and incorrectly submitted orders (Lykowski, Mahoney, 2004). The previous systems also lacked any form of analytics or reporting as to their...

Parts of this document are hidden

View Full Document
svg-one

The weakness of manual systems is their inability to create an effective, measurable baseline of performance which can be used for evaluating and improving performance over time (Purbey, Mukherjee, Bhar, 2007).
Timeline and Decision Marker Analysis of the CPOE System Implementation

The following is the timeline provides insights into how a local hospital chose to analyze and act on the inefficiencies of their CPOE process and manually-based systems. Two years ago, in 2010, losses from incomplete and inaccurate CPOE processes lead to the local hospital taking a one-time charge of $667,000 and as write-down in non-recoverable Accounts Parable of an additional $122,000. In June, 2010 the Chief Financial Officer, Chief Operating Officer and Chief Information Officer met to review why such a large loss had been incurred. The group created a task force to investigate how it had occurred. Their report was due August 1, 2010. Included in the task force were experts in value stream mapping, business process management (BPM) and experts in distributed order management systems from a local system integration partner.

On August 1, 2010 the task force presented their findings. Included was an analysis of how the existing manual processes were inadequate for the volume and complexity of the workflows they were attempting to support. Physicians, administrative staff, nurses and medical specialists all were at the presentation. At the end of the task force results discussion, the CIO invited those using the system to also contribute their ideas of hwo the system could be improved.

This third phase of the timeline included intensive cross-functional meetings involving every member of the exiting CPOE process. These included representatives from the healthcare insurance providers who were often frustrated by the errors in the existing CPOE process. Also included were administrators, physicians and nurses who needed the system to do their jobs, in addition to key members of the IT staff including the CIO. The CIO acted as the project lead on…

Sources used in this document:
References

DeVore, S.D., & Figlioli, K. (2010). Lessons premier hospitals learned about implementing electronic health records. Health Affairs, 29(4), 664-7.

Lykowski, G., & Mahoney, D. (2004). Computerized provider order entry improves workflow and outcomes. Nursing Management, 35(2), 40G-H.

Purbey, S., Mukherjee, K., & Bhar, C. (2007). Performance measurement system for healthcare processes. International Journal of Productivity and Performance Management, 56(3), 241-251.

Savsar, M., & Al-Ajmi, M. (2012). A quality control application in healthcare management using experimental design criteria. International Journal of Health Care Quality Assurance, 25(1), 53-63.
Cite this Document:
Copy Bibliography Citation

Related Documents

Software Development Life Cycle
Words: 2835 Length: 10 Document Type: Essay

Software Development Life Cycle Agile Software Development Agile software development is a popular software development process or methodology that has gained a lot of popularity in the recent years due to its effectiveness and ease of use. Firstly, it encourages collaboration and teamwork throughout the life cycle of development and this makes it easy to plan and implement. Agile software development is all about breaking a task into small chunks that make it

Software Development Life Cycle SDLC
Words: 3695 Length: 12 Document Type: Essay

Software Development Life Cycle ( SDLC) Explain Requirement process ( in SDLC) in detail. Why is this exercise important? Requirements engineering is a fundamental activity in systems development and it is the process by which the requirements for software systems are identified, systematized and implemented and are followed through the complete lifecycle. Traditionally engineers focused on narrow functional requirements. Now it is being argued by Aurum and Wohlin (2005) that focusing only

Software Development Life Cycle
Words: 1559 Length: 5 Document Type: Essay

Software Development Life Cycle Social Media Software Implementation Project Social media is an important aspect of every business today because it gives companies a unique chance to understand the customers better and to interact with them at a more personal level. A wide range of social networking tools are used by companies to attract customers to the products and services offered by the company and this makes social media software implementation essential

Software Documentation Is an Integral Part of
Words: 828 Length: 3 Document Type: Essay

Software documentation is an integral part of the software development process. However, the process is often challenging because over the course of a software development project the scope can often change and evolve several times with updates and new builds. Despite the challenges that are presented in effectively documenting the development process, the documentation that is produced can serve as a valuable asset that can be used in future projects

Software Requirements Analysis: Implications for
Words: 780 Length: 3 Document Type: Article Critique

On this aspect of agent-based SDLC performance, both approaches are limited in terms of their applicability and scalability. The reliance on heuristics can only go so far with the embedding of business, technical and organizational elements into the overall structure of an SDLC methodology (Kumar, Goyal, 2011). The reliance on an agent-based model fits well with the development of modules that are designed to align with these innately unquantifiable

Software Quality Assurance
Words: 589 Length: 2 Document Type: Term Paper

Software Quality Assurance (SQA) is defined as: "A systematic, planned set of actions necessary to provide adequate confidence that the software development process or the maintenance process of a software system product conforms to established functional technical requirements as well as with the managerial requirements of keeping the schedule and operating within budgetary confines." (Galin, cited in Food for Thought, 2005) During the 1970's, companies had difficulty delivering software within the constraints

Sign Up for Unlimited Study Help

Our semester plans gives you unlimited, unrestricted access to our entire library of resources —writing tools, guides, example essays, tutorials, class notes, and more.

Get Started Now