IT 304 Project One System Requirements Specification

IT 304 Project One System Requirements Specification (SRS) Template Complete this template by replacing the bracketed text with the relevant information in each section. If there are sections that you believe do not need to be considered in this SRS (based on the scenario provided), type in “Does not apply.” Then provide a 1- to 3-sentence rationale as to why that section does not apply for this system. The content in this file is an annotated outline specifying high-level system requirements, adapted from the ISO/IEC/IEEE 29148 International Standard (2011), page 44. References ISO/IEC/IEEE. (2011). International standard: Systems and software engineering—life cycle processes— requirements engineering 29148 . Switzerland. Retrieved from https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=6146379

System Requirements Specification Millennia Health Center Bathsheba Myers September 4, 2023 Table of Contents 1. Introduction ............................................................................................................................................. 3 1.1 System purpose ................................................................................................................................. 3 1.2 System scope ..................................................................................................................................... 3 1.3 System overview ................................................................................................................................ 3 1.3.1 System context ........................................................................................................................... 3 1.3.2 System functions ......................................................................................................................... 3 1.3.3 User characteristics ..................................................................................................................... 3 1.4 Definitions .......................................................................................................................................... 3 2. References ............................................................................................................................................... 3 3. System requirements ............................................................................................................................... 3 3.1 Functional requirements .................................................................................................................... 3 3.2 Usability requirements ....................................................................................................................... 3 3.3 Performance requirements ................................................................................................................ 4 3.4 System interface ................................................................................................................................ 4 3.5 System operations ............................................................................................................................. 4 3.6 System modes and states ................................................................................................................... 4 3.7 Physical characteristics ...................................................................................................................... 4 3.8 Environmental conditions .................................................................................................................. 4 3.9 System security .................................................................................................................................. 4 3.10 Information management ................................................................................................................ 4 3.11 Policies and regulations ................................................................................................................... 4 3.12 System life cycle sustainment .......................................................................................................... 4 3.13 Packaging, handling, shipping, and transportation .......................................................................... 4 4. Verification .............................................................................................................................................. 5 5. Appendices .............................................................................................................................................. 5 5.1 Assumptions and dependencies ........................................................................................................ 5 5.2 Acronyms and abbreviations .............................................................................................................. 5 2

from their international equivalents, several different servers around the country now function as databases. All campuses are now accessible from abroad, and some sorts of campus identification mistakes may be avoided thanks to the improved system. This creates a layer of protection over the patient database to which only authorized users have access. Therefore, there is no need to send confidential documents by international mail or fax anymore. The next section is the patient profile, which includes all information pertinent to the patient's health. In accordance with HIPPA rules, access to this data will be restricted to those members of the medical staff who have a direct and immediate need to know. Help enhance the privacy standards of MHC's day-to-day activities while also assisting in their enhancement. Due to insufficient identification, paperwork, or medical history, over a hundred times staff personnel have wrongly identified patients. Many of these occurrences have taken place over the past 12 months. Databases in the United States and elsewhere have been split, requiring different servers to provide this function internationally. The newly created technology allows access from other countries and decreases campus identification mistakes by linking all the campuses. This allows you to protect the patient database and provide only authorized users access to it. This eliminates the need to send confidential information via international mail or fax. The patient's whole medical history, including any sensitive information, will be kept in the profile. Only those members of the medical team who have direct involvement with or interaction with this patient will have access to this data. 1.3.3 User characteristics Doctors in a hospital setting are often highly busy people. They put in a lot of overtime and need easy-to-use solutions that won't let them down. In most cases, doctors want a straightforward method that streamlines their workflow and makes it easier to access patients' medical histories and information. Registered nurses (RNs) are healthcare professionals who assume responsibility for delivering comprehensive patient care across numerous specialties and different areas within the medical field. Their primary duty is to keep track of the patient's vital signs in the charts while also coordinating with the doctor and pharmacist to ensure that the right medication is given at the right time. This information must be recorded in the patient's chart and relayed to the nurse who will take over the next shift. They are responsible for managing interactions with the patient's family members who visit, and they have the authority to instruct LVNs and PCAs on when and how to monitor the patient's condition throughout the day. The role of the Business Administrator encompasses the supervision of all operational processes involved in the provision of medical care to patients inside a hospital or any other healthcare setting. They are primarily concerned with entering the patient's data, such as their insurance details, appointment times, and payment methods. The individuals have conveyed their inclination towards implementing a pre-visit online form for patients, as it would enable them to obtain pertinent information in a consolidated and uncomplicated manner. Consequently, using this approach will enable healthcare facilities to enhance patient admission and discharge rates, thereby alleviating congestion and creating a more conducive working environment for hospital personnel. 4

Within the hospital setting, the pharmacist assumes the crucial role of dispensing medications for inpatients, while also ensuring ongoing and effective contact with attending doctors and registered nurses. Furthermore, they engage in collaboration with pharmacy technicians employed inside the pharmacy setting to guarantee accurate preparation of medication doses intended for administration by nurses. The user expresses a need to access a comprehensive record of a specific patient's medication usage, while ensuring compliance with the privacy restrictions outlined in the Health Insurance Portability and Accountability Act (HIPAA). 1.4 Definitions [Defines keywords. If you use any new keywords throughout your SRS, define them in this section.] 2. References [If you use resources throughout this document, this is your reference section. Use APA formatting.] 3. System requirements [The following subsections of the SRS explain the requirements of the system that will be implemented. This section is the meat of this document, and contains some of the most important information that developers who are working on the project will need to know.] 3.1 Functional requirements [Describes the tasks or functions that the system will perform. To indicate the mandatory nature of these requirements, be sure to use “will,” “shall,” or other unambiguous language when describing the functionalities (e.g., “the system will” or “the doctor shall”).] 3.2 Usability requirements [Identifies the user needs and how the system will meet these needs.] 3.3 Performance requirements [Describes the requirements that show that the system is functioning and running properly. This includes how well a function can perform, and under what conditions it should be able to perform.] 3.4 System interface [Explains the system interface, and how it interacts with other existing systems. Also considers the system’s features and how it interacts with the user.] 3.5 System operations [Some systems behave quite differently depending on the mode of operation. When organizing by mode there are two possible outlines. The choice depends on whether interfaces and performance are dependent on mode. In this section, describe how the system operates.] 3.6 System modes and states [If the system can function in various states and modes, complete this section.] 3.7 Physical characteristics 5