Capstone Project.

Capstone Project.

            A systems integration project plays a cardinal role in management by providing valuable opportunities for success. It is an essential practice that is deemed important for improving the quality of   increases accountability of among the workers, reduces wastage of resources, and enhances independence of the health workers (Baldoni, 2010). To achieve these benefits, system integration in a hospital must have the right components and interfaces needed for the execution of the project. It is in this light that this study looks at the components and interfaces of a system integration project in a hospital.

Requirement Specification.

The two main requirements that are important when establishing interfaces and components of systems integration include goals and scope of integration. These two requirements also influence other needs such as compatibility of the software used in developing a system. With regards to goals of integration, the following requirements will be specified

System standards and reuse for all projects in the organization

• Infrastructure requirements for inter-application and management of related activities
• Management and reduction of ineffectiveness of point-to-point integration
• Balancing short term needs with long term architectural requirements
• The specific requirements on scope of the project entail the following
• Definition of the service interface
• Management, discovery and governance of life cycle changes in the interface
• Definition of system integration points
• Synchronization and propagation of data across the network

Connectivity of different elements such as bridges, protocol adapters, gateways, and connectors

The scope will entail semantic integration that will be important in determining the transformation of data and desired format for data contents. Moreover, the scope will also entail the routing, generation of message and patterns of data packet delivery to enhance security and integrity of data (Patterns & Practices, Microsoft Corporation 2002).

Process Used To Obtain Requirements

To obtain the aforementioned requirements, a system analysis process will be deployed that will enable identification of various parts of a system based on the functions and processes. For instance risk analysis process revealed the requirements that important to ensure security such as data encryption and message generation to enhance the security of data. The other analysis that was applied in the process was architectural analysis  was applied to identify needs that relate to interface of the system, data synchronization and propagation, system tools such as gateways, routers, bridges,  switches, adapters, the network layers. Architectural analysis also revealed connectivity requirements needed for the project.

The last type of analysis that was employed during identification of requirements was  change management analysis. The analysis will reveal issues related to short and long term requirements of the system’s architecture, systems standards and reuses of various tools in the system, and discovery and management of lifecycle changes. Change management analysis  will also  be applied in the determining issues related to risk that can cause  project failure in the future(Baldoni, 2010)..

 

The project will involve different participants drawn from the hospital who will play different roles to ensure its success. The stakeholders for the project will include the following groups and individuals; the board of directors of the hospital, the management, the suppliers, the technical team, and the heads of different departments in the hospital (Patterns & Practices, Microsoft Corporation, 2002).

The board of directors will play the sole responsibility of ensuring that funds for the project are available and the shareholders are informed about the goals and objectives of the project. The board will also collaborate with the management in monitoring the progress of the project.

The management of the hospital will play a set of roles which entail assessment and evaluation of the project goals, coordination of the project activities, collaborating with departmental heads to ensure that project their needs are accounted for in the project goals. The management will also play a significant role of providing adequate information to the board concerning the progress and any other relevant issue. The suppliers will coordinate with the management and the technical team to supply the right materials that will be used in the project.

 

The technical team of the project will play a continuum of roles that span from management of the project to consultation with other stakeholders. The technical will pursue specific duties which entail:

• Identification of commonalities that are needed to ensure integration of frameworks and components
• Consultation with the departmental heads to identify project needs and issues that should be included in the integration process, for instance issues such as priorities, requirements and expectations of each department.
• Implement architecture requirements such as middleware that is necessary for authorization, management and authentication of the infrastructure.
• Establish integration activities and roadmaps which should be integrated in the project
• Establish and maintain the desired artifacts which include service Meta data, patterns of design and desired architecture.

 

The last categories of stakeholders that will participate in the project are the departmental heads. These individuals will collaborate with their followers to identify specific needs that should be included in the project. For instance, the clinical departmental can raise management of health records that needs to be integrated in the system interface. The departmental heads will also play other duties which include coordination with the technical team to identify the desired pattern for integration, best initiatives to address integration challenges and identification of opportunities for service improvement and consult with the technical team on technical issues related to project integration.

 

Components and Interfaces.

 

The components that will be used in systems integration in the hospital will entail 7 main domains. These domains will be drawn from the major functions and departments of the hospital. The first domain will be physician need requirements which will encompass issues such as physician participation in decision making and participation in administration. The next domain is governance and leadership of the hospital, which touch on structure, the board and the management, and strategic decisions. The domain on financial integration will ensure that systems are properly organized to manage relationship between the payments financial receivables.

The other important domain is patient oriented and responsiveness. This domain will ensure communication of patient needs, storage of patient information; enhance access to patient information and most importantly security of patient information. This domain will be operated together with the domain on clinical integration and coordination of care. The component will establish the guideline for providing  services that are important in ensuring the quality of health care and it also integrate behavioral health initiatives into  the main care system (Baldoni, 2010).

To improve the quality of health care, there is need to integrate the component on quality. This component will improve the quality of health care services by testing the strategic initiatives and plans, provide opportunities for evidence-based activities through information sharing and leadership coordination. The domain will also provide innovative opportunities important for improvement of health care quality. The last component that will be needed to complete the composition of the domains is the component on information. This component will ensure that health records are electronically available, enable tracking of patient feedback, patient information requirements (Noble, 2011).

The aforementioned components mainly fall in the business or operation of the systems integration. However, the interplay between different layers in system integration will enable the execution and management of the component. For instance, information on various components will be available in the data layer. To retrieve information, a systems operator will have to access the information through the presentation layer and execute information requirement through the operation or business layer (Patterns & Practices, Microsoft Corporation, 2002).

Interfaces

The most common interface recommended for systems integration in a hospital is the HL7 interface. The model allows a health organization to reduce cost of investing in new technology requirements since the interface has automatic systems for adapting its requirements. The effectiveness of the HL7 emanate from its ability to define messaging and application standards and determine how information is transmitted to various sections. The interface model will enable different users of the system to perform their duties according to the organizational rules.

 

The other interface is the Common User interface which is also important in data management and integration of different functions in a hospital. CUI will enable interaction of various users, systems, operations and functions within the organization. As interface, CUI is one of the tools that is important in facilitating the interaction between the data layer, operations and the presentation of the system’s architecture.

Measurable Functional requirements

The measurable functional requirements of system integration outline what the system is expected to achieve or the businesses that the system are to do.  In this case, the measurable requirements will be identified through the guidance of various metrics. The first metric is performance whereby the system integration will be expected to improve efficiency and effectiveness of data management and information exchange. The system is expected to enhance the speed of data exchange by more than 80% within the next two years. The other metric that will be used is computability. The system will enhance computability with different software requirements to reduce inefficiency in operations. The level of compatibility of the system is expected to rise to more than 98% percent of the total components of the system (Pfluegel, Siegel & Skeen, 2006).

 

 

The next important metric for measuring functional requirement is capacity. The system will be expected to improve its capacity in order handle more operations and large amount of data from various sections within the organization. The capacity of different components tools as bridges, switches, connectors and tools will be upgraded to enhance the performance of the system.   Interoperability metric will be used to measure the level data configuration and storage. In this regard, the system will use different data languages such as SQL and XML to determine how data can be configured very easily (Noble, 2011).

Measurable Non-functional requirements

Measurable Non-functional requirements define how the metrics mentioned in functional requirements should be attained. To ensure that system improves performance and efficiency, it is important to determine whether the system can interface easily, whether the system is flexible to accommodate changes. Moreover, it   is also important to determine whether the system is user responsive in order to meet the requirement of the users. The other important non-functional measure in this case will determine the whether the system enhances data security and integrity through transcription and other data security measures (Pfluegel, Siegel & Skeen, 2006).

Assumptions of the Project Scope

• The assumptions of the project scope entail the following
• The project will define service and user interface
• The project will enable management and discovery of life cycle changes
• The project will enable synchronization of data across the system
• The project will also enhance data security, and ensure efficiency and effectiveness of operations in the hospital.

The project will also take into account all the tools that will be needed in building the system’s architecture such as bridges, connectors, gateways, and routers. The other important assumption is that the scope of the project will take into account the needs of users who rely on the system to execute their activities (Eriksson, 2008).

Pros and Cons of Proceeding with the Project

Proceeding with the project will have the following advantages:

• Enhance effectiveness and efficiency in the hospital
• Ensure proper allocation and utilization of resources for increased performance
• Enhance management of health records and customer feedback for improving health care quality

However, proceeding with the project may have some disadvantages which include the following: Increased cost of operation that will be needed for project implementation and maintenance the project will also require the organization to invest in a lot of resources that will be needed to train the employees in the hospital.

 

 

 

References

Baldoni, R., M.(2010). The Evolution of Publish/Subscribe Communication Systems. Future        Directions of Distributed Computing. Springer Verlag LNCS Vol. 2584, 2003.

Eriksson, H. (2008). Business Modeling with UML: Business Patterns at Work.  NY. John Wiley   & Sons.

Leatt, P.  & Leggat, S. (2007).Governing Integrated Health Delivery Systems: Meeting     accountability Requirements, Health Management Research Unit. Technical Report. No.   96-0,

Noble, J.  (2011).Classifying Relationships Between Object-Oriented Design Patterns      Proceedings of the Australian Software Engineering Conference.

Patterns & Practices, Microsoft Corporation. (2002). Application Architecture for .NET.    Designing Applications and Services. Retrieved from.             http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/distapp.asp.

Pfluegel, A. Siegel, L.  D. Skeen. (2006). The Information Bus – An Architecture for Extensive   Distributed Systems. Proceedings of the 1993 ACM Symposium on Operating Systems Principles.

Last Completed Projects

Are you looking for a similar paper or any other quality academic essay? Then look no further. Our research paper writing service is what you require. Our team of experienced writers is on standby to deliver to you an original paper as per your specified instructions with zero plagiarism guaranteed. This is the perfect way you can prepare your own unique academic paper and score the grades you deserve.

Use the order calculator below and get started! Contact our live support team for any assistance or inquiry.

[order_calculator]