IT 304 Project One

IT 304 Project One System Requirements Specification (SRS) 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 Bathsheba Myers 09/29/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

1 . Introduction We set out on a crucial goal to create a cutting-edge software system for Millennia Health Centre (MHC) as part of this System Requirements Specification (SRS) paper. It is an advanced healthcare provider with a global presence, offers patient care both online and in person, and has over 30 campuses in the US and another 10 internationally. The late 1990s saw the establishment of the center, which pioneered the use of online medical services. Today, motivated by technical advancements and rising patient expectations, it aspires to improve its online healthcare solutions considerably. MHC adheres to its internal policies, protecting the privacy of patient and employee data, and conducts much of its business in accordance with U.S. healthcare standards, particularly HIPAA. The company prioritizes the patient’s experience and works to ensure smooth transitions between healthcare departments. The software and technology infrastructure that MHC currently uses, however, has a number of problems that range from patient misidentifications to disjointed data systems. The envisioned software system intends to fully address these issues, build a solid foundation for healthcare delivery in the digital age, accommodate an anticipated 200% growth in patient numbers, and adhere to strict organizational, legal, and ethical requirements. These include system security, patient data privacy, and regulatory compliance. 1.1 System purpose The System's goal is to enhance patient care and streamline administrative procedures at Millennia Health Centre (MHC) to improve healthcare delivery. The target market for this publication includes patients, administrative staff, chemists, and organizational leadership. 1.2 System scope The System's scope includes dealing with a number of important problems at Millennia Health Centre (MHC). It seeks to address issues such as patient misidentification, broken international patient data connections, the need for video communication features, insufficient patient data security, antiquated technology, and departmental system fragmentation. The System's goal is to deliver a unified, effective, and secure healthcare platform that reduces misidentification, connects patient data globally, supports video collaboration, ensures strong data security, and streamlines administrative procedures. However, the System will not provide access to a patient's whole medical history to protect their privacy, and it will not let them overbook appointments to avoid conflicts and guarantee effective service delivery. 1.3 System overview The System delves into the crucial elements of the suggested System, taking into account both the technical issues of the developers and the worries of the clients/users. The System's design, data integration criteria, and performance requirements will be vitally important to developers. The System's capacity to significantly lower patient misidentification cases, establish seamless connectivity between domestic and international patient data, introduce video communication features for improved doctor- patient interactions, enhance data security protocols, and optimize organizational 3

workflows will, on the other hand, be of particular interest to clients and users. All parties engaged in the creation and use of the System are targeted by these highlights in order to meet their needs and expectations. 1.3.1 System context Within Millennia Health Centre (MHC), the System serves a wide range of stakeholders in a complex and varied environment. This entails a number of divisions like Primary Care, Specialty Care, Emergency Care, and Online Care, as well as qualified personnel like doctors, nurses, and chemists who all collaborate to offer complete healthcare services. Additionally, a significant portion of the System's user base consists of patients with a range of medical requirements, from annual physicals to urgent care. Geographically, MHC encompasses over 30 campuses in the United States and 10 schools abroad. Hence, it is crucial that the System support cross-border data sharing. It must also abide by federal laws such as the health insurance portability and accountability act (HIPAA) because it is a component of the US healthcare system. These factors highlight the requirement that it be adaptable, safe, and in compliance with industry standards, ensuring smooth operations in a complex healthcare environment. 1.3.2 System functions The main purpose of the System is to improve and streamline many facets of healthcare service delivery at Millennia Health Centre (MHC). It includes features that address the flaws in the current System and offer creative fixes. Patients can efficiently register utilizing self-service kiosks or with help from a receptionist during key operations like patient check-in. The System streamlines the administrative procedure by making it easier to verify insurance information. The accuracy and privacy of sensitive information are guaranteed through the safe management of patient medical data. The interchange of crucial patient data is improved because of the facilitation of seamless communication between healthcare providers. By assisting doctors with their examinations and offering alternatives for video consultations, the System improves the diagnosis process. Additionally, it simplifies the management of prescriptions, ensuring that chemists receive timely information and are able to resolve possible drug interactions. The solution also streamlines the checkout procedure, making it possible to schedule follow-up visits and make payments without trouble. With regard to accuracy, patient care, data security, and effective departmental coordination, this full functionality provides a significant improvement over the current System. 1.3.3 User characteristics The clients and users of the System comprise various stakeholders within Millennia Health Center (MHC), as identified through interviews with key personnel. These stakeholders encompass doctors, nurses, support staff (such as clinical assistants, receptionists, and volunteers), and patients seeking a wide range of healthcare services. Doctors require a system that aids in patient 4

examinations, documentation, and prescription management, streamlining their workflow. Nurses rely on the System for vital sign monitoring, patient data entry, and secure patient history sharing, allowing for efficient collaboration with doctors. Administrative staff, including business administration personnel, rely on the System for scheduling, insurance verification, and billing, necessitating an intuitive and streamlined interface. The technology allows chemists to access patient drug histories, enabling secure and knowledgeable prescription fulfillment. The System must be user-friendly and secure because patients interact with it to sign in, access their medical records, make appointments, and receive online care. Understanding the various needs and characteristics of different stakeholders is essential for the System's successful implementation. 1.4 Definitions The following terms are defined to help with comprehension: Stakeholders: People, organizations, or entities with a stake in the software system, such as physicians, nurses, employees in business administration, chemists, and patients. A thorough description of the functional and non-functional requirements for a software system that serves as a development roadmap is called a system requirements specification (SRS). The health insurance portability and accountability act (HIPAA) is a federal law in the US that provides security and privacy requirements for safeguarding patient health information. User acceptance testing (UAT) is a stage of software development when those using it test the functioning of the System to make sure it satisfies their needs and expectations. The visual interface of a software program that enables interaction using graphical components like buttons, menus, and icons is known as a "graphical interface" (GUI). A popular file format for documents that keeps formatting and guarantees consistent viewing on all devices is Portable document format (PDF). Electronic health record (EHR): An expanded version of an EMR that includes a wider variety of patient health data and is frequently usable by several healthcare providers. By succinctly defining significant concepts that may be used throughout the SRS document, these defined keywords seek to improve the document's readability and clarity. 5