Act6_SYI

profilehybridtek
Mo2.docx

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 for why that section does not apply to 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

Name :

Date :

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

1. Introduction

Millennial Health Center is a global organization that serves more significant parts of the world, with 30 campuses in the United States and ten campuses globally. In such a healthcare system, it is vital to keep the operability of information systems within the organization in the best interest and to meet the needs of all stakeholders in the organization. The main stakeholders are the healthcare specialists who utilize the services and the patients at the system management. The healthcare organization was among the first to embrace technology, mainly introduced in the 1990s. However, the systems are getting ineffective, and the need for a better system that synchronizes with the needs of the organization are explained in the analysis and how it will serve the interests of the organization.

1.1 System purpose

The purpose of the system is to create an integrated, modern, and advanced system that creates efficiency in operations and meets the set requirements to make the workflow in real-time in Millenia Health Care for all stakeholders, both healthcare providers, and patients. The organization is utilizing online booking for appointments and the need to meet the outcomes of data. With the system, the booking and the actual service synchronize with the needs of the patients to increase efficiency, any need for paperwork and operate in real-time to deliver care to patients.

The integrated system comes in as a unified system for the entire organization, including all departments that work for the organization, and that means as each department will use the same system network, information sharing will be eased, data management and referencing of data among the stakeholders such as patients booking an appointment and the scheduled procedure will be synchronized, pharmacists looking up for patient history on allergies will be made easier. The doctors making a diagnosis will do so in real-time.

The system will make it possible to meet the interest of consumers as it will work in all its international campuses, making it easy to access patients' data and record universally. At the same time, system integrity and restricted access will be iterated. Each user will have their records in a specific user profile that can be assigned to a doctor or nurse when needed than having an all-in-one record where each user can be accessed.

1.2 System scope

The scope of the system is to develop through a system that is customized to deal with the problems currently experienced in the existing system. For instance, over a hundred cases of inaccuracies in identifying patients existing in the current system, making it ineffective. The scope of the new system being developed will minimize misidentification of patients and the exiting procedures.

The scope will make sure the data for all patients locally in the United States and globally will be stored in a unified database which makes it possible to meet the challenge of having patients worrying about how the data is presented and how the information makes it possible to control and utilize a common database for all patients.

The advanced modern healthcare system features a video call or face chat with patients, making it easy to communicate with patients effectively and manage a sustained sharing of information. The current system only supports a chat box which makes communication to be minimal.

The system comes as an integrated system that will prioritize data security for the consumers by having restricted access to user data. That makes it easy to manage and shows that the data being managed meets the interests of consumer safety and meets the current problems. The system being and advanced modern technology which will be shared through all the departments will offer an added advantage inability to manage and control the management of outcomes and features that best explain efficiency to detail.

1.3 System overview

The central aspect of the system that the developers will need to know when developing the customized system is the organization's operation. For instance, the healthcare system currently has the option for booking an appointment online and can even come for medical check-ups without booking. The system developers need to know the problem associated with booking to overcome it, such as the concerns on when the insurance changes for consumers. That brings added burden to receptionists and even doctors when setting up the procedure, leading to calling the wrong patients.

The approach upon reaching consumers can seek self-service or a receptionist, show proof of insurance, wait to be seen by a doctor as the nurses check vita information and update the medical history and patient is directed on the procedures to follow. Naturally, such a system makes time and adds a burden. The information needs to be added in real-time when the client checks ins. Thus, developers will see that the time spent by nurses and doctors reduces repetition, and resources are utilized effectively.

1.3.1 System context

The system will be used in the Millennial Healthcare system both locally and globally. It will be ad advanced modern system that will replace the current system that has been operational since 2005. The interfaces that will be incorporated in the system include the user interface for patients within the organization and the nurse interface for the roles given, doctor's interface, which gives vital access to data, receptionist interface, and pharmacist interface, which has restricted access along with each element which makes it a sustainable efficient in managing user privacy and addressing the concerns by the users who feel the current system is not efficient.

1.3.2 System functions

The current system functions by operating each department within the organization alone, making it hard for the data management plan to share information. At the same time, it brings access to all sets of data, making it hard to show privacy and confidentiality in the consumer data. It is very effective as even a receptionist can access vital patient's data and has even led to some nurses losing jobs due to access to different patient's data in the past. The system makes it hard even for existing nurses, receptionists, and pharmacists to enjoy the system utilizing it because it is not restricted.

The new system is expected to be more elaborate and efficient as it will be customized to meet the interests and needs of the consumers, such as the ability to have restricted access of data in patients records by having different interfaces with the user can log in and gain access to the only given data sets. The system network being one makes it easy to share information within the departments and even globally safely without the need for paperwork and doing everything in real-time, which will create more efficiency and even reduce even the time utilized when serving one client in the organization from existing 10-15 minutes to very little time and that will create even higher traffic in the organization system.

1.3.3 User characteristics

The people who will be using the system include several departments in the MHC hospital, including professional staff and patients. The departments include primary care, speciality care, emergency care, online care, and check-in reception. The staff comprises the doctors, nurses, and support staff such as clinical assistants, receptionists, and volunteers. Patients will have to utilize the system mainly for preventive care, support for short-term medical conditions, support for long-term medical conditions, emergency room visits, appointments with the medical professional, annual check-ups, and visits with specialists. The admin will also utilize the system to regulate how important data can be managed and incorporated into the system.

5

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

for

why that section does not apply

to

this system.

The content in this file is an annotated outline specifyin

g high

-

level system requirements,

adapted from the ISO/IEC/IEEE 29148 International Standard

(2011)

, page 44.

References

ISO/IEC/IEEE. (2011).

International

s

tandard: Systems and software engineering

l

ife cycle

processes

r

equirements engineering

29148

. S

witzerland. Retrieved from

https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=6146379

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 for

why that section does not apply to 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