Process for eliciting requirements
The process of collecting data pertaining each segment of the company need to be clearly understood. The information will be elicited using some ways that include interviews, surveys, specification meetings and the two companies’ process documentation. For instance, a meeting is called to invite CIOs of the two companies to provide process documentation. By documenting the current processes, a baseline is provided for what the new system will look like. Surveys will be sent out to users in the two companies to feel. After analyzing data, specific groups will be invited for an interview to iron out emerging issues or provide more insight.
Stakeholders and their roles
The shareholders in an integration process include all those whose systems will be affected by the integration. IT managers in the two companies together with representatives from the insurance company, clients and employees have different roles in the integration process. IT managers will identify all the systems to be affected by the integration. A subset view, all the way to systems in the system documentation will be illustrated. This may be done using a block diagram or a chart that shows all connections between internal and external systems.
Representatives from the insurance company are party to the system integration process. This is because huge amounts of data are at stake and hence there might be a precaution to backup such data before integrating the systems (Bernardo, Casadesus, Karapetrovic, & Heras, 2012).
Components and interfaces
The new integrated system will comprise of three layers of integration. On the innermost layer are the individual subsystems that are to be brought together. There is a Point of Sale component that finds use in all sections of the facility where transactions are made. The patient management system is another component. Its use is primarily restricted to patient and doctor activities. Another component of the integrated system is billing. It comprises of all the financial aspects of patient management and extends to insurance providers. Pharmacy system is another component. The flow of drugs, supplies, and equipment in and out of the facility is managed by this system. All the components are bundled together and connected with the database using integration portal. A browser is the outermost layer of the system and connects the users to the integration portal (Bernus, Mertins, & Schmidt, 2013).
The Integrated health information system to be deployed in the hospital will have different modules at each location. In the main hospital, there is patient registration, outpatients services, lab investigation, cash counter system and drug distribution. The system should record patients upon arrival and classify them as first attendees or subsequent visitors. There is also a segment for online registration and consultation. These components have accompanying requirements that may include cash deposits or provision of patient registration numbers. In the consultation, provisions for symptoms, diagnosis, test, medication, and advice must be provided. Lab sub-system will document the investigation, using a sample id to link with the patient and only activating when charges are paid. In the pharmacy, the sub- system will detail collection of medicine from stock as per the prescription, and upon payment of all fees, documents the list of available and prescribed medicine, documents delivery of medicine to patients, refreshes drug distribution sheet, and perform other relevant activities.
The non-functional requirements of the integrated system include high availability, enhanced security, reliability and enhanced performance. The system will be accessed via a web interface at the client side and should always be available for patients, doctors, pharmacists and finance departments. In the same sense, the system needs to be highly secure such that any data related to the organization, patients and employees are kept confidential. The performance requirements should be above par. Because the system is used by a variety of sections, underperformance may lead to injuries and as such, performance metrics should be very high.
Assumptions for the scope of the project
The assumption for the implementation of this project is that resources are sufficient so that any component will not stall. A second assumption is that personnel have been trained on the use of the integrated system.
Pros and cons of the project
The integrated system will fix the issues of cost, access and mobility currently witnessed in the facility. When all the data are brought under one roof, misaligned incentives that increase the operational costs of the company are solved. There will be better service delivery for integrated frameworks because all the information is accessed anywhere at any time.
However, system integration is a complex process that requires due consideration and effort. Lack of proper planning might flag the project as failed with dire consequences for the users and the company (Galliers, & Leidner, 2014).
Bernardo, M., Casadesus, M., Karapetrovic, S., & Heras, I. (2012). Do integration difficulties influence management system integration levels?.Journal of cleaner production, 21(1), 23-33.
Bernus, P., Mertins, K., & Schmidt, G. J. (Eds.). (2013). Handbook on architectures of information systems. Springer Science & Business Media.
Galliers, R. D., & Leidner, D. E. (2014). Strategic information management: challenges and strategies in managing information systems. Routledge.