Systems Analytics and Enterprise Management 4

1. SCOPE

System Identification

The Easy health care access software, the proposed health system, contains three subsystems that are supposed to work within the large system. Due to the sole purpose of the system is to connect the client and the health care provider, it will contain two subsystem (Chudinov, 2017). The first subsystem includes the input instrumentation subsystem interface whose purpose is to acquire data from the client on the type of health service the client requires through the measurement of the process parameter and send them to the control subsystem (Amaechi, 2018). The second subsystem is the control subsystem; this is the management subsystem, which is between the client and the health care provider. The sole role of the controls subsystem is to match the service provider, who is the health care or pharmacies, and the patient who is the client (Akomolafe, 2016). Lastly, the output subsystem is the third subsystem, the role of this subsystem is to send the command received from the control either to the client or the medical health care provider in an acceptable form

System Overview

The purpose of the system is to create a platform where the client who needs health care services can access health care services easily (Abdou, 2016). Additionally, the system will create a platform where the health provider can advertise their service and get the client from. The link between the client and the medical health service provider is support or management. The nature of the system is a service system because the main purpose is service provision in the company (Akomolafe, 2016). The system will be developed in a series of three phases, which include the research phase, data analysis phase, and software development and implementation phase. The software development project will be sponsored by a private developer who will be entitled to charging for the services of the company (Akomolafe, 2016). The system development site will be the company offices where the software will be managed. Lastly, the developer of the software will include a team of researchers, information technology expert project managers, and health care officer.

System Requirements Document Overview

This study will develop a System Requirements Document (SRD) for the healthcare management system. All the steps of documentation of the project software.

The following are document are part of the SRD for the Easy health care access software. According to the event of a conflict between the requirement of this document and any other referenced document, the requirements of this document shall take precedence except as specifically provided for in the contract (Chudinov, 2017)... According to the procuring activity act of the company, all the different activities shall be dealt with conflicts shall be brought to the attention of the procuring activity.

This section provides the document in sections 3, 4, and five of this SRD document. While every effort has been made to ensure the completeness of this list, document warfighter’s are cautioned that they should meet all specified requirements of documents cited in sections 3, 4, or 5 of this specification (Demner-Fushman, 2016). Lastly, this section will provide the necessary document according to the policy and standards of the SRD.

Government Documents

Easy health care access software is subject to several government regulatory documents. The following are a document which will be listed by the government;

Non-Government Publications

The following document from a part of this document to the extent specified herein. This is according to the medical practitioner.

REQUIREMENTS

The main system has three subsystems, whose role is distinct. The subsystem includes the control subsystem, the input interface subsystem, and the output interface subsystem. According to the project's unique identifiers, every system subsystem should be checked to satisfy the requirement set (Chudinov, 2017). Through the unique project identifier, the program work breakdown structure in the pre-contract and contract work breakdown structure, each system will be checked for sufficiency.

The system is developed to observe the regulation and documentation, as shown above. This study proposes to solve the gap between the medical health doctor or provider and the client. This will be done through software development. The software will contain features which will enable the client to access various medical services remotely like the purchase of drugs, book appointment, emergency services, and therapy.

References Abdou, S. (2016). Project complexity influence on project management performance. The Malaysian perspective. MATEC Web of the conference, 66(5), 64. Akomolafe, D. T. (2016). Using Database Management System To Develop and Implement an Automated Motor Vehicle Management System. European Scientific Journal, 10(24), 313–322. Amaechi, J. C. (2018). Design and Implementation of a Hospital Database Management System (HDMS) for Medical Doctors... International Journal of Computer Theory and Engineering, 10(1), 1–6. Chudinov, I. L. (2017). The methodology of database design in organization management systems. Journal of Physics: Conference Series, 803(1), 5–10. Demner-Fushman, D. C. (2016). What can natural language processing do for clinical decision support? Journal of Biomedical Informatics, 42(5), 760–772. Lazzarini, A. &. (2015). LIGO Science Requirements Document (SRD)... New York: internal LIGO document E950018-02-E. Murdoch, T. B. (2013). The inevitable application of big data to health care. JAMA. Journal of the American Medical Association, 309(13), 1351–1352.