Proposal For Information System Solution In A Project

Task 1: Requirements Specification Report Assessment Criteria

The information system is the part of information and communication technology that refers to the technology that collects and store information for managing the business process and assist in decision-making.

The study includes the description of the information system development within a hospital. The study is divided into three sections such as Requirements Specification Report Assessment Criteria, Design Specifications Report Assessment Criteria and Performance Test Plan Assessment Criteria.

Usability Evaluation of Laboratory and Radiology Information Systems Integrated into a Hospital Information System: Giving astounding social insurance administrations can advance general wellbeing altogether. Organization of Medicine (IOM), refering to numerous investigations, affirmed that data innovation and data frameworks can assume an essential part in giving protected, opportune, compelling, and productive human services administrations (Dinh et al., 2013). Such frameworks can possibly advance patient security through giving access to astounding data amid clinical basic leadership forms. Right now, healing center data framework (HIS) is the most well-known and boundless data framework in doctor’s facilities (Nabovati et al., 2014). HIS is an incorporated framework including various subsystems which bolster data prerequisites of various offices.

Critical Factors of Information System Implementation: Inside this area of the writing survey the basic achievement factor with respect to different IS execution at different levels has been given (Kateb, Swies & Maqableh, 2014). The acknowledgment of the elements that are significant for making the execution fruitful is imperative. The basic achievement elements of IS usage can be sorted as specialized variables, ecological elements, venture administration factors, correspondence factors, venture group factors, authoritative elements and item factors. The help of the best administration, arranging of the task, planning venture, venture correspondence and numerous more are top most basic achievement factor (Laudon & Laudon, 2016). Different diaries has found that the hazard administration is likewise a basic achievement factor as far as data framework usage. Then again, few of the basic achievement elements might not have effect on the venture achievement, for example, experience of undertaking administrator, staff compensate and some more.

Components of Information System: The data framework gathers information from different I/O gadgets and different sources. Keeping in mind the end goal to store and process these information, different equipment and programming parts are required. The segments of the IT technology are as following.

• Data:This part is the fundamental of all the others. The various parts will be working on the idea of this segment.
• Hardware:The system appliances for end clients, cell phones, printers, attractive tapes for putting away information, switches, servers, firewall and numerous other equipment are required for executing the data framework.  (Gartzia et al., 2016).
• People: The end clients, support staff, administrators and numerous more individuals are a piece of the framework. The framework speaks with the clients through a GUI or graphical UI.
• Software:The product are the piece of the framework does the center work. Every one of the procedures that is destined to be gathered, will be prepared through the product. The customer association may buy programming or developed it   (Jovanovic, 2016).
• Telecommunication:The correspondence medium will be introduced for setting up correspondence between the clients for sharing crude information, pictures, writings and different things. This is otherwise called the system of the framework.

Investigating a New Framework for Hospital Information System Adoption: Doctor’s facility Information System (HIS) has been intended to give various esteems to the medicinal services group and in a roundabout way give advantages to the patients. In spite of this exclusive a couple of clinics in Malaysia have really received it, subsequently this paper by depending on auxiliary information intends to give more knowledge to the writing audit of HIS selection with regards to Malaysia. In light of this, the examination presents another mix of three hypotheses to be specific Technology Organization Environment (TOE) system, institutional hypothesis alongside Human Organization Technology (HOT-fit) model to address the moderate rate of HIS selection by Malaysian open healing facilities (Ahmadi, Ibrahim & Nilashi, 2015). We contend that each hypothetical point of view has its own particular logical influence and that a mix of these three encourage a significantly wealthier understanding of Information System (IS) execution with respect to the full scale level investigation. Along these lines, it is trusted, to speak to a few headings for future research to exhibit the relationship existing in our new proposed look into structure where clinics by focusing may make a move with a specific end goal to accomplish a superior HIS appropriation basic leadership.

1.1 Literature Review

The process initiates with the restoration of the patient. The receptionist registers the patient at the front desk. After the registration is complete, the schedule planner makes an appoint for the patient with the doctor. This purpose of this appointment is only for initial diagnosis. The doctor is responsible for doing the diagnosis and after the diagnosis is complete, the doctor will decide further treatment or release the patient. The patient is released on two conditions, if the patient treatment cannot be done or patient needs no treatment.

If the doctor believes that a doctor with other expertise can assist in patient treatment, then the doctor refers the patient to that expertise. There is a possibility that the symptoms of illness may not be clear. In this situations, the doctor will prescribe further tests prior to determining the illness.

Function, biochemical, visual and many more tests are there to do. Individual specialists carry out the tests. After completion of test, the result is sent to the doctors. These results assists the doctors to follow-up diagnosis. After the completion of diagnosis, the doctor has the choices of releasing the patient, consulting with other specialists and requesting for additional tests or therapies.  The formulation of prognosis is done on the basis of the outcome of therapies.

Functional Requirements: The functional requirements of the system are as following.

• Database:The database is the main functional requirement of the system. The system will collect the data from various inputs and users. These data need to be stored within a place from where it can retrieved if required. The database serves the purpose of storing the data.
• Report: The reporting is an essential part of the system. The system will generate report for various users such as doctor and patient. The system will be retrieving data from the database and generate few information and create the report. These report will be provided to the respective authorized users. Taken as an example, the patient report will be sent to the doctors and patient.
• Information Flow:The system transmit information to various users as well as receive the input provided by the user. The system will be consisting of various devices that are interconnected. The system will use the communication medium (wired, wireless or both) to flow the information among the de devices.
• Authorization:This is a very crucial requirement for any ICT system. This will allow the system to restrict any user from accessing the whole database. It is like preventing data flow to all the devices and making a secure path to the authorized user. Taken as an example, the doctor can see the report of the patient but the receptionist cannot and on the other hand, the receptionist can see the appointment of a patient but a doctor cannot.
• Login:Login is essential to make sure that the authorization is implemented. The system will provide each user an id. As the user will login using that unique id, the system will recognize which data to provide to that user.
• Registration:The registration is useful in terms of storing the information of the users. At the time of registration, the system generate user id and password for the individual users.

Non-Functional Requirements: The non-functional requirements are as following.

• Scalability:The scalability refers to the process of restricting the use of resources as per the business requirements. This is very essential to ensure that the system is able to provide profit at recession time.
• Availability:The system should be available to the users 24*7. The system will be handling he general procedure and emergency department. As the patient may require admission or need to urgently visit the doctor, the system must respond to the request.

Functional and non-Functional Requirement Visualization: 

In order to address cloud solution in the Hospital Information System management, the cloud solution is chosen to be Infrastructure as a Service (IaaS). This basic cloud service model acts as an infrastructure to serve multiple customers with storage and network transfer (Sultan, 2014; Lian, Yen & Wang, 2014). In this, IaaS service model, service is generally offered to deliver data transfer from single server among several servers grid to integrate the single server within VPDC (virtual private data center). The IaaS model acts as most used cloud service model along with offering SLA (service level agreements) for better performance metrics (Wan et al., 2013). Firstly, it needs to be discussed that why SLA is important for cloud solutions in this particular system design. The important points that are considered as mentioned following:

1. Variable Performance: User can view the cloud solution advertisements and they can wonder about cloud solution performance and service (Xu et al., 2014). The variable performance can be resolved using Service Level Agreement (SLAs).     
2. Over-commit to Computing Resources: The cloud solution can easily over commit to computing and cutting corners to infrastructure (Demirkan, 2013). The outcome from the over-commitment is variable and sometimes, the outcome can be unpredictable performance for the virtual infrastructure.

SLAs in cloud solution maintain some general yet specific Key Performance Indicators (KPIs); that are:

1. Volume of service:Mentioning exact amount of service in terms of hours and activities  
2. Quality of service:Mentioning exact service quality in terms of turnaround time, throughout time, and response time  
3. Peek and average load of work:Mentioning work loads so that it can be sharable within cloud components (Yao et al., 2014).
4. Volume of demand over different times of day:Mentioning demand and requirement volume on daily and hour basis
5. Penalty for cloud vendor where provider fails in meeting service requirements:Mentioning penalty aspects where vendor cannot meet SLAs  

In this Hospital Information Management system, SLA formulation needs to state some requirements to be addressed. The SLA requirements are mentioned as following:

1. Signed agreement with customers
2. Transactions by daily jobs and by hour basis for each application
3. Reporting SLA results method
4. For insufficient availability, service priority should be mentioned
5. Penalty method should be agreed when customer exceeds limits
6. Penalty method should be agreed when vendor cannot meet contract specifications
7. Schedule of actual or virtual meeting between customer and cloud vendor (if required)

Here, a general structure of SLA is shown with some parts as SLA definition, SLA components and categories, customer and service provider definition, determined qualities, and SLA parameters (He, Fan & Li, 2013). The SLA concept is shown as following:

SLA Components: An ideal SLA consists of some major parts that emphasizes on SLA with important aspects that are mentioned as following:

Purpose: SLA should provide a purpose why SLA is formed

Parties: SLA mentions which parties are to be involved and interested in the SLA and their individual jobs (Rodrigues et al., 2013).

1.2 Business Process of Hospital General Procedure

Validity period: The validity period should state the time that is covered with SLA. The validity period is defined with starting time and ending time of the service.

Scope: The scope of SLA should state the services that are to be offered; SLA structure should elaborate service levels so that customer can recognize procedure of services (Demirkan & Delen, 2013).  

Restrictions: The restrictions are set for taking essential steps regarding supply in required service levels.

Service-level Objectives: The service level objectives are considered from the customer for approval and the service level objectives include several groups of services indicators those are identified as availability, performance, and reliability (Benharref & Serhani, 2014). The part of the service level and availability takes target level for completion. The service level objectives may consider day-time restrictions that is related with describing validity.   

Service-level Indicators: The service level indicators are effective for measuring the level of the services provided from the cloud vendor.   

Penalties: The penalties described required parts where vendor cannot achieve the SLA goals (Castiglione et al., 2014). In case, the SLA is considered with external vendor, there is necessary chance of taking proper choice of concluding the contract as well.

Optional Services: The optional services are not ordinarily required from customer; however, these services might be relevant for considering as exclusion.

Exclusions: The exclusion states the parts that are not included into the SLA though those are relevant for the Service Level Agreement exceptions (Haux et al., 2013).

Administration: This administration part considers defining formed SLA with achieving and measuring the SLA goals.

In short, an SLA cannot guarantee that the organization will get service that it states, the SLA not any more than a warranty that can guarantee that service will be continuous. In particular manner, SLA is effective for picking up good service out of bad ones. On the other hand, SLA can be useful for avoiding the risks of choosing a bad service (Weaver et al., 2016). Once, a good quality service is chosen; it can mitigate the requirement of client with including quality and appropriate service. The way of designing SLA is for supplying sufficient data or performance metrics so that client can select services before making payment. SLAs are included in basic content and forms or toolkits can use them as well. The cloud vendors can prepare designs of the systems in such a way so that the measurement of services can be gathered and matched with SLA determined metrics (Russ et al., 2015; Soares et al., 2015). Therefore, most important part of any SLA is the service quality and identification of SLA parameters and metrics. These attributes in any SLA can easily measure how the service can be available to the users from the cloud vendors.  

3.1 Performance Test

In order to address the testing schedule of the risks and the entire cloud solution, the testing measures should be incorporated. The test measures could be performed in terms of choosing how the test plans should be prepared and based on the testing criteria (D’Andreamatteo et al., 2015). The test plan includes following measures:

2. Task 2: Design Specifications Report Assessment Criteria

Testing during Selection: When selection process is to be conducted for cloud solution, multiple cloud vendors should be chosen. Several options are considered when the cost is considered as well as the time and energy is considered; moreover, along with new services, possibility stays in choice making (Weaver et al., 2016). Few suppliers are yet to provide over the cloud service. The customer is dependent over single supplier once, it is called as vendor lock-in. The problems may come out to be along with supplier and therefore, some alternative suppliers can be chosen for services to be transferred. The vendor lock-in situation can be put with customer for unfavorable situation, contract negotiations can be used (Mebazaa et al., 2015). Choosing particular service and supplier, the authority should consider a timely process to consider the budget planning. The managing directors and senior managers can overview the situation, the members, customers, and other suppliers can meet agreement (SLA) before the service delivery and the vendor’s lip service can pay within selection process.

The pitfall and fault in selection so that initial objectives may fail on the implementation stage. This problem occurs when customers can get better cloud services so that different features and options will not be chosen as selection criteria (Peppard & Ward, 2016). Another pitfall can occur with more concessions along with criteria particular with particular services with best-fit requirements. The selection of cloud vendor should be divided following steps:

1. Including cloud-related aspects along with vendor selection
2. Determination of completeness and controlling selection criteria
3. Services and suppliers assessment should be conducted (Zingg et al., 2015). The example of measures that should be considered with selection process so that: “inspection of specifications and selection terms”, “asking with references and certificates”, “performance audits and inspections of the selection”, “performance of proof and concept”, and “simulation E2E business processes”.
4. Selection advice should be issued and each criteria should be represented with risk (Barello et al., 2015). Testing management and the managers can provide vendor selection report along with test results for summarizing that outcomes along with risks. Relation with IT, the risks are considered based on cost for mitigation, handling legal issues, and other stakeholder inputs are considered for risk mitigation as well.

Performance testing: When selection process is to be conducted for cloud solution, multiple cloud vendors should be chosen. Several options are considered when the cost is considered as well as the time and energy is considered; moreover, along with new services, possibility stays in choice making. Few suppliers are yet to provide over the cloud service. The customer is dependent over single supplier once, it is called as vendor lock-in (Bro-Jeppesen et al., 2015). The problems may come out to be along with supplier and therefore, some alternative suppliers can be chosen for services to be transferred. The vendor lock-in situation can be put with customer for unfavorable situation, contract negotiations can be used (Walsh et al., 2015). Choosing particular service and supplier, the authority should consider a timely process to consider the budget planning. The managing directors and senior managers can overview the situation, the members, customers, and other suppliers can meet agreement (SLA) before the service delivery and the vendor’s lip service can pay within selection process.

The pitfall and fault in selection so that initial objectives may fail on the implementation stage (Kalil et al., 2016). This problem occurs when customers can get better cloud services so that different features and options will not be chosen as selection criteria. Another pitfall can occur with more concessions along with criteria particular with particular services with best-fit requirements. The selection of cloud vendor should be divided following steps:

1. Including cloud-related aspects along with vendor selection
2. Determination of completeness and controlling selection criteria
3. Services and suppliers assessment should be conducted. The example of measures that should be considered with selection process so that: “inspection of specifications and selection terms”, “asking with references and certificates”, “performance audits and inspections of the selection”, “performance of proof and concept”, and “simulation E2E business processes” (Handayani et al., 2015).
4. Selection advice should be issued and each criteria should be represented with risk. Testing management and the managers can provide vendor selection report along with test results for summarizing that outcomes along with risks (Senaviratne et al., 2015). Relation with IT, the risks are considered based on cost for mitigation, handling legal issues, and other stakeholder inputs are considered for risk mitigation as well.  

Functionality testing: When selection process is to be conducted for cloud solution, multiple cloud vendors should be chosen. Several options are considered when the cost is considered as well as the time and energy is considered; moreover, along with new services, possibility stays in choice making (Tsai et al., 2015). There are few suppliers who are yet to provide over the cloud service. The customer is dependent over single supplier once, it is called as vendor lock-in (Peppard & Ward, 2016). The problems may come out to be along with supplier and therefore, some alternative suppliers can be chosen for services to be transferred. The vendor lock-in situation can be put with customer for unfavorable situation, contract negotiations can be used. Choosing particular service and supplier, the authority should consider a timely process to consider the budget planning (Barello et al., 2015; Weaver et al., 2016). The managing directors and senior managers can overview the situation, the members, customers, and other suppliers can meet agreement (SLA) before the service delivery and the vendor’s lip service can pay within selection process.

Functional Requirements

The pitfall and fault in selection so that initial objectives may fail on the implementation stage. This problem occurs when customers can get better cloud services so that different features and options will not be chosen as selection criteria. Another pitfall can occur with more concessions along with criteria particular with particular services with best-fit requirements (Kalil et al., 2016). The selection of cloud vendor should be divided following steps:

1. Including cloud-related aspects along with vendor selection
2. Determination of completeness and controlling selection criteria (Demirkan & Delen, 2013; Haux et al., 2013).
3. Services and suppliers assessment should be conducted. The example of measures that should be considered with selection process so that: “inspection of specifications and selection terms”, “asking with references and certificates”, “performance audits and inspections of the selection”, “performance of proof and concept”, and “simulation E2E business processes”.
4. Selection advice should be issued and each criteria should be represented with risk. Testing management and the managers can provide vendor selection report along with test results for summarizing that outcomes along with risks. Relation with IT, the risks are considered based on cost for mitigation, handling legal issues, and other stakeholder inputs are considered for risk mitigation as well.

Testing after completion: When selection process is to be conducted for cloud solution, multiple cloud vendors should be chosen. Several options are considered when the cost is considered as well as the time and energy is considered; moreover, along with new services, possibility stays in choice making. Few suppliers are yet to provide over the cloud service (Lian, Yen & Wang, 2014). The customer is dependent over single supplier once, it is called as vendor lock-in. The problems may come out to be along with supplier and therefore, some alternative suppliers can be chosen for services to be transferred. The vendor lock-in situation can be put with customer for unfavorable situation, contract negotiations can be used (Rodrigues et al., 2013). Choosing particular service and supplier, the authority should consider a timely process to consider the budget planning. The managing directors and senior managers can overview the situation, the members, customers, and other suppliers can meet agreement (SLA) before the service delivery and the vendor’s lip service can pay within selection process.

The pitfall and fault in selection so that initial objectives may fail on the implementation stage (Yang, Li & Niu, 2015). This problem occurs when customers can get better cloud services so that different features and options will not be chosen as selection criteria. Another pitfall can occur with more concessions along with criteria particular with particular services with best-fit requirements. The selection of cloud vendor should be divided following steps:

1. Including cloud-related aspects along with vendor selection
2. Determination of completeness and controlling selection criteria
3. Services and suppliers assessment should be conducted (Demirkan, 2013; Yao et al., 2014). The example of measures that should be considered with selection process so that: “inspection of specifications and selection terms”, “asking with references and certificates”, “performance audits and inspections of the selection”, “performance of proof and concept”, and “simulation E2E business processes”.
4. Selection advice should be issued and each criteria should be represented with risk (Wan et al., 2013). Testing management and the managers can provide vendor selection report along with test results for summarizing that outcomes along with risks. Relation with IT, the risks are considered based on cost for mitigation, handling legal issues, and other stakeholder inputs are considered for risk mitigation as well.

Furthermore, the cloud vendors should be interviewed about the SLA and the service quality as well so that the entire service could be effective for Hospital Information System.

References

Ahmadi, H., Ibrahim, O., & Nilashi, M. (2015). Investigating a new framework for hospital information system adoption: a case on Malaysia. Journal of Soft Computing and Decision Support Systems, 2(2), 26-33.

Barello, S., Graffigna, G., Vegni, E., Savarese, M., Lombardi, F., & Bosio, A. C. (2015). ‘Engage me in taking care of my heart’: a grounded theory study on patient–cardiologist relationship in the hospital management of heart failure. BMJ open, 5(3), e005582.

Benharref, A., & Serhani, M. A. (2014). Novel cloud and SOA-based framework for E-Health monitoring using wireless biosensors. IEEE journal of biomedical and health informatics, 18(1), 46-55.

Bro-Jeppesen, J., Annborn, M., Hassager, C., Wise, M. P., Pelosi, P., Nielsen, N., … & TTM Investigators. (2015). Hemodynamics and vasopressor support during targeted temperature management at 33 C Versus 36 C after out-of-hospital cardiac arrest: a post hoc study of the target temperature management trial. Critical care medicine, 43(2), 318-327.

Castiglione, A., Pizzolante, R., De Santis, A., Carpentieri, B., Castiglione, A., & Palmieri, F. (2015). Cloud-based adaptive compression and secure management services for 3D healthcare data. Future Generation Computer Systems, 43, 120-134.

Non-Functional Requirements

D’Andreamatteo, A., Ianni, L., Lega, F., & Sargiacomo, M. (2015). Lean in healthcare: a comprehensive review. Health Policy, 119(9), 1197-1209.

Demirkan, H. (2013). A smart healthcare systems framework. It Professional, 15(5), 38-45.

Demirkan, H., & Delen, D. (2013). Leveraging the capabilities of service-oriented decision support systems: Putting analytics and big data in cloud. Decision Support Systems, 55(1), 412-421.

Dinh, H. T., Lee, C., Niyato, D., & Wang, P. (2013). A survey of mobile cloud computing: architecture, applications, and approaches. Wireless communications and mobile computing, 13(18), 1587-1611.

Handayani, P. W., Hidayanto, A. N., Sandhyaduhita, P. I., & Ayuningtyas, D. (2015). Strategic hospital services quality analysis in Indonesia. Expert Systems with Applications, 42(6), 3067-3078.

Haux, R., Winter, A., Ammenwerth, E., & Brigl, B. (2013). Strategic information management in hospitals: an introduction to hospital information systems. Springer Science & Business Media.

He, C., Fan, X., & Li, Y. (2013). Toward ubiquitous healthcare services with a novel efficient cloud platform. IEEE Transactions on Biomedical Engineering, 60(1), 230-234.

Kalil, A. C., Metersky, M. L., Klompas, M., Muscedere, J., Sweeney, D. A., Palmer, L. B., … & El Solh, A. A. (2016). Management of adults with hospital-acquired and ventilator-associated pneumonia: 2016 clinical practice guidelines by the Infectious Diseases Society of America and the American Thoracic Society. Clinical Infectious Diseases, 63(5), e61-e111.

Lian, J. W., Yen, D. C., & Wang, Y. T. (2014). An exploratory study to understand the critical factors affecting the decision to adopt cloud computing in Taiwan hospital. International Journal of Information Management, 34(1), 28-36.

Mebazaa, A., Yilmaz, M. B., Levy, P., Ponikowski, P., Peacock, W. F., Laribi, S., … & McDonagh, T. (2015). Recommendations on pre?hospital & early hospital management of acute heart failure: a consensus paper from the Heart Failure Association of the European Society of Cardiology, the European Society of Emergency Medicine and the Society of Academic Emergency Medicine. European journal of heart failure, 17(6), 544-558.

Nabovati, E., Vakili-Arki, H., Eslami, S., & Khajouei, R. (2014). Usability evaluation of Laboratory and Radiology Information Systems integrated into a hospital information system. Journal of medical systems, 38(4), 35.

Peppard, J., & Ward, J. (2016). The strategic management of information systems: Building a digital strategy. John Wiley & Sons.

Rodrigues, J. J., De La Torre, I., Fernández, G., & López-Coronado, M. (2013). Analysis of the security and privacy requirements of cloud-based electronic health records systems. Journal of medical Internet research, 15(8).

Russ, S. J., Sevdalis, N., Moorthy, K., Mayer, E. K., Rout, S., Caris, J., … & Darzi, A. (2015). A qualitative evaluation of the barriers and facilitators toward implementation of the WHO surgical safety checklist across hospitals in England: lessons from the “Surgical Checklist Implementation Project”. Annals of surgery, 261(1), 81-91.

Senaviratne, S. L., Opanayaka, C. J., Ratnayake, N. S. L., Kumara, K. S., Sugathadasa, A. M., Weerasuriya, N., … & Silva, H. J. (2015). Use of antivenom serum in snake bite: a prospective study of hospital practice in the Gampaha district. Ceylon Medical Journal, 45(2).

Soares, K. C., Baltodano, P. A., Hicks, C. W., Cooney, C. M., Olorundare, I. O., Cornell, P., … & Eckhauser, F. E. (2015). Novel wound management system reduction of surgical site morbidity after ventral hernia repairs: a critical analysis. The American Journal of Surgery, 209(2), 324-332.

Sultan, N. (2014). Making use of cloud computing for healthcare provision: Opportunities and challenges. International Journal of Information Management, 34(2), 177-184.

Tsai, T. C., Jha, A. K., Gawande, A. A., Huckman, R. S., Bloom, N., & Sadun, R. (2015). Hospital board and management practices are strongly related to hospital performance on clinical quality metrics. Health Affairs, 34(8), 1304-1311.

Walsh, T. S., Salisbury, L. G., Merriweather, J. L., Boyd, J. A., Griffith, D. M., Huby, G., … & Murray, G. D. (2015). Increased hospital-based physical rehabilitation and information provision after intensive care unit discharge: the RECOVER randomized clinical trial. JAMA internal medicine, 175(6), 901-910.

Wan, J., Zou, C., Ullah, S., Lai, C. F., Zhou, M., & Wang, X. (2013). Cloud-enabled wireless body area networks for pervasive healthcare. IEEE Network, 27(5), 56-61.

Weaver, C. A., Ball, M. J., Kim, G. R., & Kiel, J. M. (2016). Healthcare information management systems. Cham: Springer International Publishing.

Weaver, C. A., Ball, M. J., Kim, G. R., & Kiel, J. M. (2016). Healthcare information management systems. Cham: Springer International Publishing.

Wu, Y., Cegielski, C. G., Hazen, B. T., & Hall, D. J. (2013). Cloud computing in support of supply chain information system infrastructure: understanding when to go to the cloud. Journal of Supply Chain Management, 49(3), 25-41.

Xu, B., Da Xu, L., Cai, H., Xie, C., Hu, J., & Bu, F. (2014). Ubiquitous data accessing method in IoT-based information system for emergency medical services. IEEE Transactions on Industrial Informatics, 10(2), 1578-1586.

Yang, J. J., Li, J. Q., & Niu, Y. (2015). A hybrid solution for privacy preserving medical data sharing in the cloud environment. Future Generation Computer Systems, 43, 74-86.

Yao, Q., Han, X., Ma, X. K., Xue, Y. F., Chen, Y. J., & Li, J. S. (2014). Cloud-based hospital information system as a service for grassroots healthcare institutions. Journal of medical systems, 38(9), 104.

Zingg, W., Holmes, A., Dettenkofer, M., Goetting, T., Secci, F., Clack, L., … & Pittet, D. (2015). Hospital organisation, management, and structure for prevention of health-care-associated infection: a systematic review and expert consensus. The Lancet Infectious Diseases, 15(2), 212-224.