IT 304 Project One System Requirements Specific.- Angran (1)

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 HealthCenter Courtney Angran 26/11/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 ............................................................................................................. 4 1.3.3 User characteristics ......................................................................................................... 4 1.4 Definitions .............................................................................................................................. 4 2. References 4 3. System requirements 4 3.1 Functional requirements ......................................................................................................... 4 3.2 Usability requirements ........................................................................................................... 5 3.3 Performance requirements ..................................................................................................... 5 3.4 System interface ..................................................................................................................... 5 3.5 System operations .................................................................................................................. 6 3.6 System modes and states ........................................................................................................ 6 3.7 Physical characteristics .......................................................................................................... 6 3.8 Environmental conditions ...................................................................................................... 7 3.9 System security ...................................................................................................................... 7 3.10 Information management ..................................................................................................... 7 3.11 Policies and regulations ........................................................................................................ 7 3.12 System life cycle sustainment .............................................................................................. 8 3.13 Packaging, handling, shipping, and transportation .............................................................. 8 4. Verification 8 5. Appendices 8 5.1 Assumptions and dependencies .............................................................................................. 8 5.2 Acronyms and abbreviations .................................................................................................. 8 2

1.3.2 System functions Mobile applications and web access will be available for patient access to medical data. Scheduling or finding appointment dates, and updating personal information. There will be access for medical personnel on company devices and terminals on-site. 1.3.3 User characteristics Doctors can be very busy people and most of the time cannot wait on systems that lag. Access to patient records and medical history needs to be easy, quick and not time consuming. Nurses are in charge of providing care to patients with a spectrum of needs. They will be the primary users of the medical system by documenting, researching and informing the doctor or aspects regarding patient care and the record. They also need to easily communicate with other nursing staff who will be taking over care when applicable. They also need access to notify family and communicate where applicable. Business admins oversee operations as far as registrations, payment methods, ensuring that billing is properly coded and that data is correctly entered for a seamless transfer of data as well as maintaining facilities appointment schedules. Pharmacists will be responsible for maintaining patient prescription records, dispensing medications as required and ensuring medication stocks get refilled when close to depletion. They will also communicate with other pharmacists, pharmacy technicians, doctors, nurses and business administrators for any reason related to medications. Using a full medication history is key when thinking about HIPAA legalities, we want to ensure that medications which should not be mixed are not mixed. (HealthIT, 2017) 1.4 Definitions --- 2. References HealthIT. (2017, September 15). Improved patient care using ehrs . HealthIT.gov. https://www.healthit.gov/topic/health-it-and-health-information-exchange-basics/improved- patient-care-using-ehrs M6 Technology. (2023, September 28). The vital role of data backups in Healthcare Facilities . M6 Technology Group IT Consulting. https://m6works.com/the-vital-role-of-data- backups-in-healthcare-facilities 3. System requirements The sections following describe the implementation of the system's requirements. These sections are key details for the project developers. 4

3.1 Functional requirements Patients will be granted the ability to check-in via a kiosk, receptionist or application/website. Patients will have the ability to visit any of our campuses which belong to the Millenia HealthCenter network as all our locations will be connected and have access and the ability to update medical files. Our new system will ask specific demographics to ensure that the correct patient record is accessed for the visit or appointment. For the patient they will be able to use the system to scan insurance cards, enter or update a phone number, address and reasons for visits. Medical professionals will be able to quickly access the insurance information, check coverage before a visit or procedure, and let the patient know if they are fully or partially covered. Any medical professional wishing to access patient records will need to provide two-factor authentication, and access will only be granted when necessary. When filling out a patient's prescription, for example, doctors can utilize the system to inform pharmacists about any allergies, current medications, and patient sensitivities. Before departing, patients can schedule an appointment or use the system to schedule one on their own schedule. The architecture of this new system will make it simple for patients to see their primary care physician virtually, regardless of the reason for their need. 3.2 Usability requirements Per HIPAA our system must ensure that data is not being sold or distributed to external vendors or other partners without users consent. Our system must also be within accordance with an IEEE- established code of ethics. All data from our organization is to be kept accurate, up-to- date, and completely confidential. Our system will be designed to always require verification of the patient to ensure accuracy. (M6 Technology, 2023)When specific updates or modifications are made to a patient's file or records, alerts will be sent out for security reasons. Alerts about personal information (phone number, address), lab results, requested lab results, prescription drugs, treatments, and appointment summaries are just a few of the things that could be sent out. The system satisfies user needs by enabling patients to check in ahead of time and to communicate virtually with their doctor. Through our system, the patient can also access all of their medical records, which can enhance their satisfaction with their doctor and the quality of their medical care. (HealthIT, 2017) 3.3 Performance requirements A reliable internet or Wi-Fi connection is required for the system to function, and it must also function properly. There would probably be delays if the connection was either weak or unreliable. It won't function if there is no connection. With the exception of an outage or surge, the badge or code should always function for the medical professional. The patient's safety and the system's integrity are the only reasons why the badge or code will not function if it is forgotten. 3.4 System interface A front page will appear on the application or website when a patient chooses to access it. If there are no appointments scheduled, the option to update or confirm the information is accurate will be displayed. Viewing insurance, bills, and application preferences will be 5

Healthcare facilities use electronic health records, or EHRs, to send data effectively, manage inventories, and drastically cut down on paper waste. Combining workflows and systems utilized by all departments into a single system designed specifically for Millennia HealthCenter and all of its campuses will also save costs. The information flows very well, particularly when all the information that is required is readily available and neatly organized into a single file on a single system, eliminating the need to request information from different departments within the same company. (HealthIt, 2017) Along with improving previously underperforming areas of the health center, this also results in better appointments, grateful and involved patients, and an increase in accuracy in the care provided. Millennia is a healthcare network that upholds an ethics code for moral, legal, and ethical reasons. 3.9 System security Using a VPN is the first step toward protecting the network so that medical professionals can access the system. Millennia will only allow VPN access. Patients can check in at the kiosk or through the app by entering their group number and patient identification, which is done for security reasons. The employees at Millennia will all follow the dress code. Since all data is encrypted, patients and staff must constantly verify and authenticate themselves. Software will also need to automatically update and be reviewed by IT to guarantee there are no breaches. 3.10 Information management Via coding and revenue, informatics, data analytics, and information governance, our system will manage information across all databases and communicate with numerous other systems. In order to maintain HIPAA compliance, regulations and patient privacy information management are essential. (Health IT, 2017) To make sure we are abiding by legal requirements and processing patient requests for private health information, all communication will be recorded and closely watched. If a patient is prescribed a drug, the pharmacy will receive it, check that the drug will be effective for the patient based on the information supplied, and then fill the prescription. All medical professionals should receive a well-designed and secured badge in addition to a unique code or password that allows them to access our secure network. 3.11 Policies and regulations Millennia HealthCenter shall implement user access controls in a manner that upholds confidentiality and guarantees adherence to the moral standards delineated in the ACM code of Ethics and Professional conduct. Only those who are authorized would be able to access health data following two factor authentication in accordance with HIPAA. Under HIPAA, doctors are prohibited from discussing patient information with individuals who are not connected to the patient or designated to assist them. This includes privacy, security, and breach notification regulations. The system is configured to automatically lock after a certain number of unsuccessful attempts to log in. (M6 Technologies, 2023) Complete control over user access permissions and upkeep of an employee log new will be granted to the database administrator. 7

3.12 System life cycle sustainment Sometimes the team's only chance to identify any concerns or problems is through feedback. We will include a feature in the app that allows patients and healthcare providers to report any issues or worries that come up while using it. Every now and then, patients using the self-serve kiosk will be asked to complete a brief survey. Doctors will assess the system as well as the company questionnaires every three months. These surveys are essential because the primary users of the system must effectively use it in accordance with its intended purpose. The relevant team will review and take appropriate action on any feedback received. 3.13 Packaging, handling, shipping, and transportation When our system is operational, medical professionals will use it via workstations or company devices on the secured network, and patients will use it through the application. The simplicity of communication with the physician or patient, depending on the user, is another way that this is an extra package. Lastly, the software and coding developers create our system. 4. Verification Look for coding errors, show that the interface is operating correctly, test to make sure all features are operating as planned, then evaluate the outcomes and correct any problems that were discovered. Every user should depend on the company-provided SOP and the company-provided maintenance procedures to keep the system functioning properly. The fundamental components of the system will continue to work if all regulations and directives are followed. One of the fantastic built-in features is 24/7 IT support for any issues that may come up. 5. Appendices 5.1 Assumptions and dependencies HIPAA as most patients trust their medical professionals to be diligent and protect their data either in person or through virtual care. There is an assumption of patients being able to call their primary care physician at the click of a button via the app. Millennia HealthCenter and all of its campuses are connected through this system. Our system provides a smooth way for all patients to access their medical files, history and information, our medical professionals' devices must be linked to the secured company network and all patients must access the application via a strong internet connection or the features may not work. 5.2 Acronyms and abbreviations ACM Association for computing machinery HIPAA Health insurance portability and accountability act IEEE - Institute & electrical & electronic engineers SOP- software operating procedure SRS - Software requirement specification VPN - Virtual Private Network 8