Clinical Information System - Report Example

SYSTEM DEVELOPEMET LIFE CYCLE FOR UMUC CLINICAL INFORMATION SYSTEM The System undergoes a series of development cycle and showing step wise for the whole cycle. The resource needed during implementation is clearly shown and explained their importance. TABEL OF CONTENTS Contents ABSTRACT 2 TABEL OF CONTENTS 3 INTRODUCTION 4 1.1.DEVELOPMENT LIFE CYCLE 5 1.3.SYSTEM DESIGN, PROGRAMMING AND TESTING. 7 1.4.IMPLEMENTATION. 8 1.4.2.CO-ORDINATION 9 1.4.3.REPORTING 10 1.4.4.KEY ELEMENTS AND COMPONENTS OF THE SYSTEM. 10 1.5.MAINTENANCE 11 2.CONCLUSION 12 3.REFERENCES 13 INTRODUCTION The development of information technology and health information systems has had a major impact on Clinical Care. Quality Clinical Information is becoming a powerful tool for decision-making and management. However, because of the growing quantity of information, nurses need an efficient information system in order to be able to use all available information to the Patients maximum benefit. Therefore this paper documentation is an Electronic Health Care Data System for designed to give out a faster and quicker overview for the EUMUC student Health care service Clinic by providing a detailed information of the Development Life Cycle including the use of Servers, backups Emailing, Internet Accessibility and Software’s used in Clinical Computer System. 1. CLINICAL INFORMATION SYSTEM DEVELOPMENT. An information system can be defined as the use of computer hardware and software to process data into information to solve a problem. The term Clinical Information System (CIS) refers to a group of systems used within a Clinic that support and enhance health care. The CIS comprises two major types of information systems: Clinical Information Systems and Administrative Information Systems. Clinical information systems are large, computerized database management systems that support several types of activities: medical, nursing, laboratory, diagnostic, pharmacy, radiology. Administrative information systems support the process of client care by managing non-clinical, client-related information, including demographics, codes for procedures and insurance. Clinical and administrative information systems may be designed to meet the needs of one or more departments or functions within the organization. They can be implemented as stand-alone systems, or they may work with other systems to provide information sharing and seamless functionality for the users. The Clinical Information System can be developed from the start by information technology professionals co-operating with healthcare professionals in the hospital. 1.1. DEVELOPMENT LIFE CYCLE A SDLC is the traditional method used by organizations for large IT projects. The SDLC entails of sequential processes by which information systems are developed: analysis, design, programming, testing, implementation, and maintenance. A Clinical Information System is a complex system, and Clinic Attendants have a key role to play in practically all phases of its development. The beginning of the (life) cycle is a clear vision of the business process. What do we want to do with the new system? How are we going to do it? What do we need for the system to operate efficiently? So, we must determine the purpose and goals of the project, assure the necessary financial resources, carry out cost-benefit and feasibility analyses, and form a project team consisting of a variety of specialists and draw up a project plan. It is very important to appoint a suitable project leader, who must come from within the organization. The ideal project leader is a senior manager who has a working knowledge of all aspects of the business and good people skills to interface with the entire user community; delegation of the role to a junior person in the organization diminishes its perceived importance to both management and the user community. To ensure that continuity in the project is maintained, it is also imperative that the project leader be assured of a permanent position in the organization once the project is considered to be complete. 1.2. SYSTEM ANALYSIS. System analysis is the investigation of the business problem that the organization plans to solve with an information system. This step is of extreme importance. In too many cases, an information system is developed or purchased to achieve vague and somewhat idealistic goals that cannot possibly be accurately measured. An example of this type of goal would be to "reduce papers or save time." What exactly does that phrase mean? Reduce what papers, save what time? A business needs analysis is a careful, step-by-step examination of how our business functions. It includes the collection of data from a variety of areas within an organization. For this purpose we can use various techniques, such as process observation, interview and documentation study. Clinical Officers are analysts, they have been taught to analyze the situation thoroughly before making critical decisions. These skills and knowledge must be used when analyzing hospital processes. The quality of the information system to be developed will depend largely on our understanding how the real world functions and our knowledge of specific features of our work. Numerous analyses have shown that the majority of errors in information system development projects are the result of incorrect definition of requirements due to lack of understanding of the field of business. The end product of this stage is a model of the existing system and a set of information requirements. The model of the existing system illustrates all its procedures and their functional interdependence. It provides a clear insight into the structure of the existing system, facilitates communication between system analysts and users, and is of help in solving the problem of complexity. It serves as a basis for identification of opportunities for improvement. The next step is modelling the future system. The model of the existing system may differ considerably from that of the future one, especially if our objective in developing the new system is also to optimize and rationalize our procedures. Requirements that support the philosophy and practice of different professions must be carefully defined. Expectations regarding data output and effects of the new system must be defined on the basis of measurable results. In order that the system can provide quality support to all its end users, the requirements of individual departments and professions must be coordinated at a point where their information needs meet. 1.3. SYSTEM DESIGN, PROGRAMMING AND TESTING. The deliverable of the system design phase is the technical design that specifies the user interfaces, hardware, software, databases, and telecommunications and how these components are integrated. Development of application software belongs among activities of programming and testing. Generally, it is impossible to determine with certainty if an application that has been developed is correct, without errors. We usually select trial data and check if the required tasks are performed correctly. The co-operation of Clinical Officers in the phase of testing an application is obligatory. We must verify that the application is functional, that it meets all legal requirements and that information generated from data that has been entered into the system (statistical data, comparative analyses) is appropriate. A well-designed Clinical Information System must provide data for decision-making and management. 1.4. IMPLEMENTATION. Implementation is the method of changing from the old system to the new one. A Clinical Information System is a complex system. We may use different strategies: parallel, direct, pilot or phased. In a direct conversion, the old system is cut off and the new system is turned on at a certain point of time. A pilot conversion introduces the new system in one part of the hospital organization for a period of time, so that it can be assessed. If it works properly, it is then acquaint with in other parts of the Clinic. A phased conversion presents modules of the newly introduced systems, such as individual modules, in stages until the entire new system is operational. Clinical Officers can play an extremely valuable part in the implementation phase because they have more direct hands-on interaction with and knowledge of the different departments than perhaps any other member of the project and implementation team. Nurses also provide helpful input into the restatement of policy and procedures and the workflow within healthcare organization departments during a system implementation. Implementation of the new system can result in various changes, which can be minor (soft - variation) or radical (hard - redirection). Soft changes refer to ordering the existing condition and automation of work and are designed to simplify processes. Hard changes are fundamental changes of processes, relationships and rules. When implementing a CIS, we are changing the practices and procedures in our hospital. Studies show that fear of changing traditional procedures may lead to a decline in morale and workplace satisfaction. The main reasons for the development of resistance to such changes are unrealistic expectations, alteration of traditional procedures, a new way of work, inadequate involvement of users in information system development and, last but not least, fear of the unknown. In order to reduce possible opposition of hospital staff during the implementation phase we need to organize a workshop or a kick-off meeting to inform staff of the goals and objectives of the project. Communicating expectations, defining desired outcomes, and letting everyone know about their respective roles and commitments will set the stage for the forthcoming events. For successful implementation of an information system, it is important to prepare a strategy, appoint a suitable team and make sure that the end users understand the system and actually use it. Information, education and satisfaction of the users are essential. In each department a team should be appointed that will participate in the implementation of the system, follow its course and report any difficulties that may arise. Very important skills needed during the implementation phase are communication, co-ordination and reporting. 1.4.1. COMMUNICATION. Clinical Officers must inform end users about the importance of the system and the reasons for changing it. A new system does not mean automation of old processes but rather support for a new, more efficient way of work. It is essential that users understand how the system functions and accept it as an aid in their daily work and not as a new additional task. They must be provided with detailed instructions for its use, including descriptions of individual procedures and the users responsibilities. This will reduce the likelihood of complications, ensure smooth operation and increase user satisfaction. The rules for carrying out individual procedures and mechanisms for safe access to and use of the data must be defined already during the planning phase. 1.4.2. CO-ORDINATION Co-ordination includes organizing meetings, planning education, planning implementation of the information system and setting priorities. The implementation of a new system may evoke negative reactions on the part of its users, which may be the result of inadequate computer knowledge or fear of change. A basic computer course covering keyboard skills, screen navigation and software help functions should be organized before the implementation phase. Training in the use of the new system must be organized in the form of workshops. Continuous assistance to system users must be provided. 1.4.3. REPORTING By regularly informing the management about the progress of implementation of the hospital Information system, we secure the managements support for the project and maintain it. Exchange of information between departments contributes to better understanding of the patient care process and better co-operation between clinical departments and auxiliary services. Changes in processes that are part of Clinical Care lead to changes in the processes of other units 1.4.4. KEY ELEMENTS AND COMPONENTS OF THE SYSTEM. There are many various key elements and components which will be key in implementing the Clinical Information Systems. These includes the following; 1.4.4.1. NT SERVER The network server is providing basic file serving, printer sharing and DHCP. These are users and security settings on network shares, though the clients are not logging into the domain, so the security is more or less moot. Operating System: Windows Computer Name: NT-Server_MainClinicSite Domain Name: CLINIC_DOMAIN Processor: X86 Family 6, Model 7, Stepping 2 Memory: 512MB HDD: 1 -85 GB Drive, 3 Partitions 1.4.4.2. PRINTERS The network at the main Clinic site has a number of printers, the majority of which are connected to the practice management system. 1.4.4.3. EMAIL SERVER The clinic should use ASP mail server provided by Internet Service with accounts. 1.4.4.4. UER MANAGER The Clinic will be using First Names and Last Names for all the users where their passwords are set to never expire. The flowing groups are likely to be in use Billing, Accounting, Clinic, Finance operations, Students database, Human resources and etc. 1.5. MAINTENANCE Maintenance includes debugging the program (elimination of errors), bring up-to-date the system to house changes in business conditions and adding new functionality to the system. The procedure for submitting requests for a change must be carefully defined. Experience shows that it is best to appoint a person who will be responsible for communication and co-ordination between users and programmers. In Clinical Information Systems, this role, for the needs of Clinical Care, is taken over by Clinical Officers. The process of CIS development is not completed with its implementation and use. The information system lives, changes and grows to include an increasing number of work processes. After the completed implementation of the system, we must not forget to provide continuous support to its users, organize refresher courses and training for new users, supervise the use of the system, organize working meetings and make every effort to solve promptly any problems that may arise. 2. CONCLUSION Clinical Officers play an important role in all phases of development of a hospital information system. Their role changes from that of analysts in the analysis phase through that of organizers, coordinators and mediators in the implementation phase, to that of revisers in the phase of evaluation. Therefore nurses must be taught already during the training process to analyze the systems within which they function and solve problems on the basis of acquired information. Since organizational changes and implementation of information technology are mutually dependent processes, the implementation of a Clinical Information System for UMCU calls for attention to be focused on human factors and organizational culture. Experience shows that successful acceptance of a new CIS by the nursing staff depends on a number of factors. It is important to: a) Ensure active co-operation of nurses already in the phase of strategic planning; b) Appoint a Clinical Officer in each department to co-ordinate implementation of the system. c) Form a team of coordinators from individual departments to encourage exchange of experience. d) Provide sufficient staff to assist with the implementation. e) Organize a kick-off meeting or a workshop for nurses to provide them with information on new procedures, nurses responsibilities in using the new system, and expected effects of the new system on nurses work, patient care and the hospital as a whole; f) Train Clinical Officers and other experienced nurses to assist with the training of other nursing staff. When planning and implementing an information system, we must adopt a unified methodological approach, prepare quality standardized documentation, develop a flexible system that can be readily modified, and actively involve the end user. Continuous communication between system developers and users is of vital importance. The organizational changes that will occur with the implementation of the new system must be anticipated and presented to its users as a positive development and not as an additional task in their daily work. The participation of experts from all relevant fields in all phases of the project is essential for its successful completion. 3. REFERENCES 1) Hawley, W. L., Tariq, H., & Gardner, R. M. (1988, November). Clinical Implementation of an Automated Medical Information Bus in an Intensive Care Unit. In Proceedings/the... Annual Symposium on Computer Application [sic] in Medical Care. Symposium on Computer Applications in Medical Care (pp. 621-624). American Medical Informatics Association. 2) ICN: Participation of Nurses in Health Services Decision Making and Policy Development. http://www.icn.ch/psmanagement00.htm, 2007. 3) Snyder-Halpern, R. (2001). Indicators of organizational readiness for clinical information technology/systems innovation: a Delphi study. International journal of medical informatics, 63(3), 179-204. 4) C. M. Ruland: Developing CLASSICA: A Decision Support System (DSS) for Nurse Managers. Nursing Informatics 2000. One Step Beyond: The valuation of Technology and Nursing. Clineguide CD-ROM, 2000. 5) Van de Velde, R., & Degoulet, P. (2003). Clinical information systems. Health Informatics Series, 41. 6) T. Hebda, P. Czar, C. Mascara: Handbook of Informatics for Nurses and Healthcare Professionals. 3rd ed. Pearson Prentice Hall. (2005), 120-121. 7) E. Turban, R.K. Rainer, R.E. Poter: Introduction to Information Technology. 3rd ed. John Wiley & Sonc, Inc. (2005). 489-495. 8) V. Prijatelj: Success Factors of Hospital Information System Implementation: What must go right? Medical Informatics Europe 99. Studies in health technology and informatics (vol. 68). Peter Kokol et al. Amsterdam. IOS Press. Tokyo: Ohmsha. (1999), 197-200. 9) B. Jaeckle: The Role of Nurse as System Analyst. Nursing Informatics: Where Caring and Technology Meet. Springer-Verlag New York Inc. (2000), 103-111. 10) V. Prijatelj, M. Črv: Development and implementation of nursing information system. Informatica medica slovenica. (2004), 63-67. 11) S. Jenkins: Nurses Responsibilities in Implementation of Information Systems. Computers in Health Care. Nursing Informatics: Where Caring and Technology Meet. Springer-Verlag New York Inc. (2000). 216-231. 12) R. ODonohue, P. Rawstorne: The Nurses Dream: Development and Implementation of a Clinical Information System for the Point of Care. Nursing Informatics 2000. One Step Beyond: The valuation of Technology and Nursing. Clineguide CD-ROM. 2000. 13) Pollard, C. E., Gupta, D., & Satzinger, J. W. (2010). Teaching systems development: a compelling case for integrating the sdlc with the item lifecycle. Information systems management, 27(2), 113-122. 14) Pearlson, K., & Saunders, C. S. (2004). Managing and using information systems: A strategic approach. Hoboken, NJ: Wiley. 15) Walls, J. G., Widmeyer, G. R., & El Sawy, O. A. (1992). Building an information system design theory for vigilant EIS. Information systems research, 3(1), 36-59. 16) Kushniruk, A. (2002). Evaluation in the design of health information systems: application of approaches emerging from usability engineering. Computers in biology and medicine, 32(3), 141-149. 17) Haag, S., Cummings, M., & Dawkins, J. (1998). Management information systems. Multimedia systems, 279, 280-297. 18) Haag, S., Cummings, M., & Dawkins, J. (1998). Management information systems. Multimedia systems, 279, 280-297. 19) Hirschheim, R., Klein, H. K., & Lyytinen, K. (1995). Information systems development and data modeling: conceptual and philosophical foundations (Vol. 9). Cambridge University Press. 20) Sawyer, S. (2001). A market-based perspective on information systems development. Communications of the ACM, 44(11), 97-102. Read More