IT 304 Project One System Requirements Specification
docx
keyboard_arrow_up
School
Southern New Hampshire University *
*We aren’t endorsed by this school
Course
304
Subject
Information Systems
Date
Apr 3, 2024
Type
docx
Pages
5
Uploaded by ElderHeronMaster1052
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
Aellaha Ali February 27, 2024
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
Millennia HealthCenter (MHC) has been serving its client since 1990 by providing convenient services such as in-person and online portal. To accommodate the growing demand of online support and patient care, this document will outline the integration of a new software. This includes the resources required to implement the system, test and installation. The goal of this integration is to be develop in nine months, softest for three months and then install the new software throughout the MHC
facilities. Therefore, within a year, this new program will be fully launch and utilized throughout the company with full capacity. 1.1 System purpose
To achieve MHC vision, this new program would enhance the efficiency of the healthcare professionals by allowing them to manage patient appointments, ensure operations, integrate global patient data, ensure secure data, protect patient privacy, maintain accurate records and increase patient inflow while following HIPPA rules. This would also be a user-friendly interface which would allow a better communication between medical professionals, patients, shareholders and medical company such as pharmacy and labs.
1.2 System scope
The new system is established by considering all aspects of the MHC offices to create one unified system that could enhance patient experience while safeguarding their data. Furthermore, the new system will also eliminate patient and procedure misidentification by ensuring that all database complies with HIPPA rules, providing universal access to only authorized users of MHC offices while including all elements of patient’s visit such as appointments, insurance information, diagnosis, lab results, medical history, pharmacy, prescription history and doctor notes. 1.3 System overview
The new system would play a significant role in integrating all parts of a patient’s visit such as patient’s sensitive information, appointments/scheduling, insurance information, medical records and doctor notes. Another significant feature of this system would be the infrastructure of authentication and access restriction while preventing unauthorized users from gaining access to patients’ information. The authentication infrastructure design would be a two-step verification or credentials that could only provide access to authorized users and for those with limited access. 1.3.1 System context
The new system provides fast, convenient ways of handling patients medical concern from primary, specialty, emergency to online care. The new system is a one unified system which means that from check-in to check-out all patient care would be in one system but with restricted access based upon job responsibilities or duties. For example, the business administrator would be able to utilize this database for scheduling, sending appointment reminders and confirming the patient. The nursing staff will have restricted access to electronic record with the ability to record vital health information and update medical history. The doctor will have access to all the patients’ medical database such as labs, medicine, concerns, notes and
etc. while, the pharmacist could access medicine history and prescribed medicine. Additionally,
patients would have access to the portal as well whether it is to schedule their annual check-up 3
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help
or to asking questions about their health. It is a tool that protects customer information, provides conveniences while supporting the medical professionals with up to date data, access to appointments/scheduling, patient notes, history, and would be able to take care of patient’s needs, medical conditions globally. To interface with the new system, an international database has been updated in order to include patient globally where MHC provides services. 1.3.2 System functions
The current system of MHC contains various steps prior to seeing a doctor which consumes a lot
of time, more exposure of client’s privacy, misinterpretation of records, loss of medical history or documentation errors. However, the new system resolves all of these issues. It enhances customer experience by providing patients with the ability of scheduling an appointment, checking-in and descripting their concerns prior to the appointment. Not only this is patient focus, but also for medical professionals. It prepares the medical professional for the appointment or read for the client. The administrator could easily request information via portal
or update payment/billing information. The nurse could utilize the system to record vital health information, view old report for changes, send notes to the doctor without having the customer wait. This would avoid two current issues. One recording on chart which could be lost or stolen and second saves time from seeing the doctor in person. The nurse could keep assisting patients. The doctor could analyze everything while the pharmacists could record the prescription and access old medicines. The new system would avoid security exposure such as fax papers, mailed records, paper folders of patients records while making it convenient, fast, secure for everyone and help with the operations.
1.3.3 User characteristics
Doctors: Study medicine and take an oath to do no harm when it comes to the treatment of their patients. They are very busy individuals that work long hours. It is crucial for them to have current and accurate data information in front of them to have proper diagnosis. Bad data results in wrong diagnosis. Doctors prefer to utilize one system that is simplified while have the able to complete all their tasks in one site. They would like to save time while be able to view all medical information at one software. Nurse: are members of medical profession who is accountable for providing comprehensive care
to patients for a wide range of specialties such as monitoring patient’s status, administrating inoculation, updating the patient’s needs, behavior, improvements, health declines, collecting samples and ensuring properly labeled and sent off for review, all while ensuring the information is accurately enter into the system. the nurse simultaneously communicates with the doctors about a patient need. A nurse prepares accurate appointment data and not overbooking appointments, easy access to drug allergies medical report, lock screen security, restrict access of medical records, authentications of a customer prior to access medical records and the ability to schedule appointments.
Business Administrator: responsible for logistical processes that occurs from the time a patient arrives until they depart. They prefer a system to minimizes overbook appointments, a system that could rapidly provide updated insurance coverage information, a system that could monitor
the reason for the visit, identity verification and reliable accesses patient electronic data. 4
Pharmacist: are responsible to fill the patient’s prescription as soon as possible, but also in a safe and cautious manner. Ensures existing medication, the new medication will not have any harmful drug interactions, cost of certain drugs and provides alternative drug to reduce the costs. Pharmacist prefer a system that allows them to view patient’s drug history, receive an alert message whenever the system searches for drug interactions that are not compatible with each other.
5