Information_System_Briefing

Information System Briefing When selecting an information system for a health care organization, there are processes that must take place. One of the processes is selecting and acquiring an information system, one that will be a success for this particular health care organization. In order for the health care organization to have success, the information system must be chosen very carefully. Once a health care organization has finalized its contract with the vendor to acquire an information system, the system implementation process begins. Selecting the right system does not ensure user acceptance and success; the system must also be incorporated effectively into the day-to-day operations of the health care organization and adequately supported or maintained. Whether the system is built in-house, designed by an outside consultant, leased from an application service provider (ASP), or purchased from a vendor, it will take a substantial amount of planning and work to get the system up and running smoothly and integrated into operations. Implementing a new system (or replacing an old system) can be a massive undertaking for a health care organization. Not only are there workstations to install, databases to build, and networks to test but there are also processes to redesign, users to train, data to convert, and procedures to write. There are countless tasks and details that must be appropriately coordinated and completed if the system is to be implemented on time and within budget—and widely accepted by users. While attending to these tasks, there are other issues that must be attended to. Organizational and behavioral issues will have to be addressed also. (Wagner et al, 2009). Each application has a targeted audience. The functionality and cost increases exponentially as capabilities increase to meet a broader need. However, most can be purchased on a modular basis, allowing an organization to purchase the types of functionality required to meet immediate needs, while providing scalability for future expansion. Some system's capabilities do overlap. The question that needs to be answered is whether the majority of the systems' capabilities are needed now or in the near future. An understanding of the organization's future goals is needed to guard against over or under buying on system capabilities. Some systems are designed to meet the specific needs of only selected types of organizations, such as insurance companies, pools, captive, and third-party administrators. ERPSs, in particular, have targeted industries, such as manufacturing or service, which drive the system's design. Although an ERPS may have some risk management functionality, typically it is based on data collected from an interfaced RMIS or CMIS, or from financial information manually entered into the application. Typically, an ERPS is purchased as a function of decisions made by the organization, rather than a single function (such as risk management or finance) within the organization. From a true risk management standpoint, an ERPS is not typically considered within the selection process (Tillinghast & Perrin, 2001). What is the process for selecting and acquiring an information system' System Implementation begins once the organization has acquired the System and it continues through the early stages following the go-live date. The go-live date is the date when the system is put into use for everyone. This system must have a high level of support from its support team. There are three things that must be devoted to this project. The three things are sufficient staff, time and the resources. Without these three things, the project will not be a success. One of the first things that must be done is to organize an Implementation Team. The responsibility of this team is to plan, coordinate and manage all aspects of the Implementation System. The Implementation Team should consist of a Strong Project Leader, System Champions, and Key Individuals from clinical areas. Having the right people on the Implementation Team is very critical and very important. One of the first issues of business is to determine what the organization hopes the project will achieve. In conclusion, Planning is everything. Buying the application that meets immediate needs but lacks scalability or the capability for future expansion can be a costly mistake. Which application best meets your needs may be a function of flexibility and cost, rather than immediate needs. References Tillinghast, Anita S., Perrin, Towers (2001). Information Systems: Which type is right for your organization' Retrieved on March 26, 2012 from http://www.irmi.com/expert/articles/2001/schoenfeld04.aspx Wager, Karen A. Lee, Frances Wickham, Glaser, John P. (2009). Managing Health Care Information Systems: A Practical Approach for Health Care Executives. ( 2nd ed.). Hoboken, NJ: John Wiley & Sons, Inc.,