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

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

The System shall facilitate the secure exchange of patient histories and current vitals between nurses and doctors through in-person consultations and system documentation. The System would provide professionals with a platform to thoroughly examine patients and document their findings in order to guarantee complete and accurate medical records. In order to guarantee that patient records accurately reflect the most recent information, the System will allow medical practitioners to update patient medical histories and treatment statuses quickly. In order to give patients and healthcare practitioners a comprehensive perspective, the System will synchronize patient instructions, treatment options, and testing requirements. The System must seamlessly interface with pharmacy systems in order to notify pharmacists of new patient prescriptions. They will be able to process drug orders quickly, check for any allergies, and suggest less- priced options thanks to this. The solution will let patients finish the checkout check out procedure, including paying and scheduling follow-up appointments, to simplify administrative procedures. To protect patient data, ensure that only individuals with the appropriate authorization can access specific patient records, and meet ethical and legal standards for data privacy, the System must have robust security mechanisms in place. By offering a modern, rapid, and responsive user interface that facilitates simple navigation for all users, the System will boost speed and efficiency.] 3.2 Usability requirements The System is carefully crafted to successfully address the wide range of needs of patients and healthcare providers. Patients' entire experience will be improved by a simple check-in process, shorter wait times, and simplified checkout procedures. An integrated platform for data entry, access, and updates, as well as a user-friendly interface for recording patient information and performing thorough examinations, would increase the efficiency of healthcare personnel, including nurses and doctors. In order to ensure safe and effective drug delivery, chemists will receive timely alerts of new prescriptions and access to pertinent patient data. The implementation of strong security measures will also address the ethical and legal requirements required for healthcare operations, protecting patient data and ensuring data privacy. While addressing the needs and challenges within the current processes, these system solutions seek to improve the user experience. 3.3 Performance requirements Response Time: Under typical operating conditions, the System must respond to user requests, like loading patient records or making appointments, in under two seconds. 7

Up to 1,000 concurrent users must be supported by the System without performance degradation in order for patients and healthcare professionals to use it at the same time. System Uptime: The System must maintain a 99.9% uptime minimum. To reduce interruption, planned maintenance and update downtime should be scheduled outside of busy times. Data Retrieval: To ensure that healthcare professionals can quickly access patient information during appointments, patient data retrieval from the database should take up to one second per record. Data Update: To guarantee the accuracy and timeliness of patient information, the System should provide real-time data updates, with changes appearing instantly in the patient's medical records. Data management and storage: The System must effectively handle and keep track of patient records, supporting a minimum of 1 million patient profiles and the data that goes with them while still operating at peak efficiency. 3.4 System interface The system interface acts as a vital link for smooth communication between various stakeholders and current systems. It is made with the needs of the user in mind to specifically address those of medical professionals, such as nurses, business executives, chemists, and patients. A seamless and effective experience is ensured by tailored user interfaces that are each in line with the roles and responsibilities of various stakeholders. Business executives can effectively manage scheduling and billing procedures, while doctors and nurses will have access to thorough patient records. The System will also be closely integrated with already-existing ones, such as the MHC online portal and the global patient database, to guarantee that patient information is accessible from any place. Additionally, sophisticated patient data management and appointment scheduling features will expedite operations, while real-time messaging and video conferencing capabilities will improve communication among healthcare personnel. In essence, the system interface is created to enable users, make tasks simpler for them, and promote the best possible patient care and administrative effectiveness. 3.5 System operations Both the online and in-person modes of the System's operation are specifically designed to cater to the various needs of Millennia Health Center's patients. Online Mode: With the help of a user-friendly web interface, patients can access healthcare services from a distance in this mode. Using video conferencing and real-time messaging capabilities, patients can set up online 8

be restricted or unavailable. To reduce disruptions, any planned maintenance is communicated to patients, healthcare providers, and other stakeholders. Services provided in person continue with little disruption, and urgent situations are handled immediately. 4. Offline Mode: The System may go into offline mode in the event of unanticipated technical difficulties or network concerns. The capability for online consultations may be reduced, but patients can still access their information. Healthcare providers continue to deliver in-person services as usual while waiting for internet connectivity to be restored. 5. Remote Operation State: This mode is very important for healthcare workers who must access the System remotely while on the go or working from multiple places. It guarantees secure access to patient data and enables medical professionals to give online consultations, examine patient records, and write prescriptions. By utilizing a variety of states and modes, Millennia Health Centre is able to respond to various situations while preserving the quality of its patient care and fundamental healthcare services. The ability of the System to adapt to the various needs of patients and healthcare professionals is facilitated by its adaptability and responsiveness. 3.7 Physical characteristics Millennia Health Centre (MHC) adapts its system deployment to a variety of user needs and scenarios by adopting a comprehensive strategy. This covers the provision of healthcare on-site at more than 30 American campuses and 10 overseas institutions, ensuring direct access to services. In addition, MHC has a strong online presence thanks to its website and web-based applications, which enable remote access for clients and medical staff members via web browsers and mobile devices. This online component makes it possible to monitor prescriptions, conduct virtual consultations, and communicate in real time. Users are empowered to seamlessly switch between in- person and online healthcare encounters because of MHC's hybrid deployment strategy, which harmoniously combines on-site and online capabilities. MHC relies on a robust data center infrastructure to enable these deployments, protecting patient data, medical records, and system functionality while strictly adhering to data security and privacy regulations, including HIPAA compliance. This adaptable strategy for system deployment highlights MHC's dedication to providing secure, effective, and accessible healthcare services in a variety of contexts. 3.8 Environmental conditions The new software system's adoption at Millennia Health Centre (MHC) has the potential to have a substantial impact on a number of environmental factors, going beyond the scope of medical technology. On the political front, the System's compliance with legal requirements, such as the Health Insurance 10

Portability and Accountability Act (HIPAA), is essential for safeguarding patient rights and data privacy and aligning MHC with federal healthcare regulations. Additionally, given its global presence and the increasingly linked nature of the globe, MHC's capacity to securely manage patient data and follow local privacy laws is essential. The new System's acceptance and user adoption are crucial to its social success. It should improve patient experience, simplify patient care procedures, and give medical staff effective resources to deliver high-caliber care. A seamless user experience promotes system trust, which is advantageous to personnel and patients. The System's integration across numerous MHC sites and departments needs organizational alignment with the organization's policies, especially in terms of data exchange and delivering a consistent patient experience. Last but not least, improved resource allocation, decreased errors, and higher operational efficiency would all benefit the corporate environment. The software system's optimization of healthcare workflows may result in cost savings that would help MHC remain financially viable while also enhancing the standard of service and patient outcomes. The new System is poised to play a transformational role in reshaping the healthcare scene at MHC and beyond in the complex interaction of political, social, organizational, and business elements. 3.9 System security To safeguard patient information, privacy, and system integrity, Millennia Health Center's (MHC) new software system must meet stringent security criteria. Strong security methods, such as secure log-on procedures, multi-factor authentication for authorized users, strict password restrictions, and data encryption both in transit and at rest, will be used by the System to ensure the appropriate security levels. By limiting user privileges based on responsibilities, access control measures will make sure that only authorized workers can see and update patient records. Additionally, thorough audit trials will monitor system activity to spot any suspicious or unauthorized operations quickly and take appropriate action. To protect patient data and maintain data confidentiality, integrity, and availability, these security methods adhere to industry standards and regulations like HIPAA. 3.10 Information management Data security, integrity, and privacy will be prioritized in the management of information within the new software system at Millennia Health Centre (MHC). The System will put in place strong data management procedures to solve these issues. Patient information will be kept in encrypted, secure databases with user- role-based access controls. To guarantee the integrity of the data during transmission and integration, interactions with other systems and interfaces will adhere to predetermined protocols. Only with the explicit user agreement and in accordance with rigorous privacy regulations will data exchange with outside 11

and optimized to meet better changing user needs while retaining high-quality healthcare services. Overall, a proactive and dedicated team, as well as a robust feedback loop, will ensure that the new software system at MHC maintains its high level of quality and dependability. To ensure consistent and dependable functioning, it is essential to make sure that the System's hosting infrastructure is properly managed and maintained. In order to guard against unexpected service outages or data loss, this may require concerns relating to data centers, cloud hosting, backup systems, and disaster recovery plans. The underlying infrastructure supporting the program will be meticulously managed to ensure operational stability and data security even though it may not require physical packaging or delivery. 4. Verification Several strategies and techniques will be used to test the functionality of the new software system at Millennia Health Centre (MHC): Testing and Validation: Strict testing, including unit testing, integration testing, and system testing, will be carried out at different stages of development. To find and fix any flaws or problems, this will entail modeling user interactions, data inputs, and system activities. User Acceptance Testing (UAT): To ensure that the System satisfies the needs and expectations of MHC's stakeholders, including doctors, nurses, business administration personnel, chemists, and patients, UAT will be conducted. This guarantees that the program complies with their requirements and workflows. Continuous quality assurance techniques will be used to monitor and enhance the System's functionality, security, and dependability. System quality will be preserved with the aid of routine audits and reviews. Performance evaluation: To make sure the System can manage the anticipated load, the System's performance will be assessed under various circumstances. For the purpose of locating and resolving performance bottlenecks, this includes load testing, stress testing, and scalability testing. Security Testing: To find weaknesses and guarantee the safety of patient data, rigorous security testing will be carried out. Penetration testing, vulnerability analyses, and compliance checks with laws like HIPAA are all included in this. Compliance and Documentation: Extensive documentation outlining system requirements, design, and operational procedures will be produced. To make 13

sure the System complies with organizational and federal policies and laws like HIPAA, it will be validated. User Training: To guarantee that users can use the System correctly and traverse it, adequate training programs will be made available to them. This reduces errors brought on by user confusion. Data Validation: To guarantee the correctness and integrity of data entered into the System, data validation procedures will be put into place. This helps avoid problems brought on by inaccurate or lacking information. Feedback Mechanisms: The System would have feedback mechanisms, such as user surveys and feedback forms, to enable users to regularly report problems or suggest improvements. Monitoring and analytics: To monitor system performance, user behavior, and potential problems, tools for continuous monitoring and analytics will be employed. With a proactive approach, issues can be found and fixed right away. Together, these verification techniques guarantee that the software system satisfies its functional requirements as well as quality, security, and compliance standards, finally giving MHC a trustworthy and effective healthcare solution. 5. Appendices 5.1 Assumptions and dependencies A number of important presumptions and dependencies are necessary for the Millennia Health Centre (MHC) to install the new software system successfully. First off, it is believed that all parties involved—including physicians, nurses, employees in charge of business operations, chemists, and patients—will take part in the user acceptance testing (UAT) and feedback procedures. Their participation is essential to confirming and improving the System's specifications so that it effectively satisfies their needs. Second, it is a fundamental presumption that all federal rules, particularly the Health Insurance Portability and Accountability Act (HIPAA), will be followed. To ensure the security and privacy of patient data, the System's development and implementation must comply with all applicable laws and regulations. Thirdly, the project relies on the existence of crucial assets, including qualified development teams, suitable hardware infrastructure, and financial resources. These tools are necessary for the software system's effective development, testing, and deployment. 14