Scribd
Upload
22 views10 pages

Healthcare Maintenance System SRS

The document provides a software requirements specification for a healthcare maintenance system. It outlines the purpose of developing an automated system for patient scheduling, diagnosis notes, appointment reminders, paperless billing and reports. It describes the intended users of the system including doctors, patients, developers and medical staff. Finally, it provides an overview of the key product functions such as patient details, lab reports, billing and appointment management.

Uploaded by

Mr Ammar
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
22 views10 pages

Healthcare Maintenance System SRS

The document provides a software requirements specification for a healthcare maintenance system. It outlines the purpose of developing an automated system for patient scheduling, diagnosis notes, appointment reminders, paperless billing and reports. It describes the intended users of the system including doctors, patients, developers and medical staff. Finally, it provides an overview of the key product functions such as patient details, lab reports, billing and appointment management.

Uploaded by

Mr Ammar
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Software Requirements

Specification
for

Healthcare Maintenance System

Prepared by: Mridul Tripathi 16BCE0672

Suvronil Basu 16BCE0655

Vellore Institute of Technology, Vellore

Date Created: 29/01/2018


Software Requirements Specification for Healthcare Maintenance System Page ii

Table of Contents
Table of Contents .......................................................................................................................... ii
Revision History ............................................................................... Error! Bookmark not defined.
1. Introduction ..............................................................................................................................1
1.1 Purpose ........................................................................................................................................ 1
1.2 Document Conventions ............................................................................................................... 1
1.3 Intended Audience and Reading Suggestions ............................................................................. 1
1.4 Product Scope ............................................................................ Error! Bookmark not defined.
1.5 References ................................................................................................................................... 1
2. Overall Description ..................................................................................................................1
2.1 Product Perspective ..................................................................................................................... 1
2.2 Product Functions ........................................................................................................................ 2
2.3 User Classes and Characteristics ................................................................................................. 2
2.4 Operating Environment ............................................................................................................... 2
2.5 Design and Implementation Constraints ..................................................................................... 2
2.6 User Documentation .................................................................................................................... 2
2.7 Assumptions and Dependencies .................................................................................................. 3
3. External Interface Requirements ...........................................................................................3
3.1 User Interfaces ............................................................................................................................. 3
3.2 Hardware Interfaces .................................................................................................................... 3
3.3 Software Interfaces ...................................................................................................................... 3
3.4 Communications Interfaces ......................................................................................................... 3
4. Domain Model ............................................................................ Error! Bookmark not defined.
5. System Features (Use Cases) ..................................................... Error! Bookmark not defined.
5.1 Use Case 1 ................................................................................. Error! Bookmark not defined.
5.1.1 Name: .................................................................................... Error! Bookmark not defined.
5.1.2 Goal: ...................................................................................... Error! Bookmark not defined.
5.1.3 Input: ..................................................................................... Error! Bookmark not defined.
5.1.4 Output: .................................................................................. Error! Bookmark not defined.
5.1.5 Main Scenario: ...................................................................... Error! Bookmark not defined.
5.1.6 Pre-condition: ........................................................................ Error! Bookmark not defined.
5.1.7 Steps: ..................................................................................... Error! Bookmark not defined.
5.1.8 Post-condition ....................................................................... Error! Bookmark not defined.
5.1.9 Exceptional Scenario 1 ......................................................... Error! Bookmark not defined.
5.1.10 Example................................................................................. Error! Bookmark not defined.
5.2 Use Case 2 (and so on) .............................................................. Error! Bookmark not defined.
6. Other Nonfunctional Requirements ......................................... Error! Bookmark not defined.
6.1 Performance Requirements ....................................................... Error! Bookmark not defined.
6.2 Safety Requirements .................................................................. Error! Bookmark not defined.
6.3 Security Requirements .............................................................. Error! Bookmark not defined.
6.4 Software Quality Attributes ...................................................... Error! Bookmark not defined.
7. Other Requirements .................................................................. Error! Bookmark not defined.
Appendix A: Glossary...................................................................... Error! Bookmark not defined.
Appendix B: Analysis Models ......................................................... Error! Bookmark not defined.
Appendix C: To Be Determined List .............................................. Error! Bookmark not defined.
Software Requirements Specification for Healthcare Maintenance System Page 1

1. Introduction

1.1 Purpose
Developing a Health Care Maintenance which provides automated case management, patient scheduling,
diagnosis notes, electronic mail integration to remind patient about their appointment, electronic revisit
letter with paperless environment, Point of Sales (POS), inventory for spectacles, lenses and sundries and
unlimited custom and pre-built reports.

1.2 Document Conventions


This document is edited with the use of the standard Times New Roman font with a text size of 11 and 14
depending on the type of text (title, paragraph, details, etc) this software is built using HTML, CSS,
JavaScript on front end and SQL server as backend.

1.3 Intended Audience and Reading Suggestions


This system is built keeping in mind the development of various healthcare aspects and areas.
The document is intended for the readership of every individual that is concerned with the healthcare system
directly or indirectly. These readers may include but are not limited to: 1) Doctors 2) Patients 3) Web
Developers 3) Chemists 4) Physicians 5) Specialists 6) Staff Nurses, etc. The reader is suggested to have an
open mind while going through the document as it deals with a very vast and versatile field.

1.4 References
1) An integrated approach to software engineering, Third edition by Pankaj jalote
2) HTML, CSS, JavaScript – Jon Duckett.
3) SQL server – Joseph L Jordan

2. Overall Description

2.1 Product Perspective


This project gives the procedural approach how a patient gets treatment, details about date of treatment and
finally depending on different criteria like room allocated, lab reports, treatment and medicine taken, how
billing is calculated, etc. During billing health card facility is also considered. At the same time this project
also deals with the different mediums that can be built between different stakeholders For example, A
website between customers and the hospital is crucial to give the customers a better outlook. For the
development of the website we also need web developers. Hence, how all the stakeholders are related to
each other is enumerated in this document.
Software Requirements Specification for Healthcare Maintenance System Page 2

2.2 Product Functions


The data represented in healthcare maintenance system application will perform the following major

 Patient Details: - It includes inpatient and outpatient details.


functions:

 Lab reports

 Billing Details

 Appointment Details

 Correct diagnosis of the diseases

This software will help to calculate the bill much quicker and simpler way. This will also ensure that
the diagnosis of the disease is accurate and every customer’s satisfaction and stakeholders’
satisfaction. This enables the organization to keep the information in an efficient and systematic way.

2.3 User Classes and Characteristics


This software is developed such that total appearance of the product to make it more user friendly.
The operator will be provided with login id and password. General users with basic computer skills can use
this software. The different classes of users may include: 1) Customers/ Patients 2) Doctors 3) Chemists 4)
Physicians 5) Web Developers, etc.

2.4 Operating Environment


The following software and hardware operating environments have been used in the software:
1) Windows 10
2) Web page using CSS, HTML and JavaScript

2.5 Design and Implementation Constraints


This will help the doctors or users to view the records of the patients immediately whenever necessary. They
can also calculate the bill of the particular patients. This software also has the ability to add, update and
delete the record whenever needed. This project will help to smoother the process of the hospital activities.

2.6 User Documentation


This project is divided into different modules, each module has its own significance and is independent of
the other. Once in the library/module, you can further narrow your search by selecting Product Type and
Manual Type using the integrated search wizard.
Software Requirements Specification for Healthcare Maintenance System Page 3

2.7 Assumptions and Dependencies


This project assumes that there will be a database of medical records hosted by a server. The server assumes
it will be installed with a high-speed Internet connection to communicate with the users. The software being
developed assumes that the users have an access to the Internet from either a cellular or Wi-Fi connection to
establish a connection between the application and the medical record repository. The web version of the
project assumes that the user has a computer with an Internet connection and a web browser to access the
online version of the software.

3. External Interface Requirements

3.1 User Interfaces


User interface is designed in a user-friendly manner and the user, in another end he has to give the order, for
that he will interface with keyboard and mouse.

3.2 Hardware Interfaces


1) OS – Windows 10
2) Hard disk – 1 TB (1024 GB)
3) RAM – 8 GB
4) Keyboard – Standard QWERTY keyboard for interface
5) Mouse – Standard mouse with 2 buttons and touchpad.

3.3 Software Interfaces


1) Front end – HTML, CSS, JavaScript.
2) OS – Subline Text
3) Back end – SQL Server

3.4 Communications Interfaces


Windows, HTML, CSS Website.
Software Requirements Specification for Healthcare Maintenance System Page 4

4. Domain Model

5. System Features (Use Cases)


A use case is a methodology used in system analysis to identify, clarify, and organize system requirements.
The use case is made up of a set of possible sequences of interactions between systems and users in a
particular environment and related to a particular goal. It consists of a group of elements (for example,
classes and interfaces) that can be used together in a way that will have an effect larger than the sum of the
separate elements combined. The use case should contain all system activities that have significance to the
users. A use case can be thought of as a collection of possible scenarios related to a particular goal, indeed,
the use case and goal are sometimes considered to be synonymous.

5.1 Health Maintenance System

5.1.1. Name: Health Maintenance system for concerned Users

5.1.2 Goal: To find the correct connection between the disease and symptom and provide
accurate predictions of the disease and fixing an appointment

5.1.3. Input: User Inputs data of his own details including symptoms and past medical history
Software Requirements Specification for Healthcare Maintenance System Page 5

5.1.4. Output: Accurate prediction for disease from symptoms and fixing appointment.

Main Scenario:

5.1.6. Pre-condition:

User must be aware of the symptoms the person is having and reporting it accurately

5.1.7. Steps:

Step1:

The user inputs a series of answers to some basic question along with symptoms

. Step2:

The data is processed and matched with a disease profile

Step3:

The disease according to its severity is given a ranking and the user is prompted to make a doctors’
appointment

Step4:

The doctors meet with their patient and recommends medicine and pharmacy.

Step5:

The User gets a medical certificate and medicines and is treated for the disease.

Post-condition:

The User must attend for a re-appointment.

Exceptional Scenario 1:

If the severity of the disease is not high, then appointment not required.
Software Requirements Specification for Healthcare Maintenance System Page 6

Example

6. Other Nonfunctional Requirements

6.1 Performance Requirements


The system might require heavy databases as it has to handle millions of data and hence would
require hardware with better processors. The website to be made has to try to not lag so as to satisfy the user
as soon as possible considering the urgency of any medical treatment

6.2 Safety Requirements


There are possibilities that the system might describe a wrong disease considering the number of
similar symptoms shared by in-numerous diseases. There is no reason to worry as there is an option of cross
checking with doctors appointed considering their time of diagnosis

6.3 Security Requirements


Due to security reasons it is recommended to give the patients name and identification as a proper certificate
would be issued if a dire diagnosis occurs. The certificate would be issued digitally and credentials would be
taken from what the user has input. Incorrect authentication can lead to problems with the legal system. The
software is not responsible for such an event.
Software Requirements Specification for Healthcare Maintenance System Page 7

6.4 Software Quality Attributes


The software is a website which would provide accurate disease predictions for concerned users and
potential patients. Doing a herculean task requires a robust network and great user interface which we
provide.

7. Other Requirements
There are other requirements we would cover after the SRS. Some of them are initialized below:

Appendix A: Glossary
Software engineering
The establishment and use of sound engineering principles in order to obtain economically software
that is reliable and works efficiently on real machines.
The application of a systematic, disciplined, quantifiable approach to the development, operation, and
maintenance of software; that is, the application of engineering to software.
The systematic activities involved in the design, implementation and testing of software to optimize its
production and support. [Canadian Standards Association]
Software entropy
The amount of disorder in a software system
Software metric
A software metric is a combination from measures of attributes belonging to a software product, or to
its development process, which shows quantitatively some of its characteristics
Ease of use
The ease with which people of various backgrounds and qualifications can learn to use software
products and apply them to solve problems. It also covers the ease of installation, operation and
monitoring.

Engineering
The profession in which a knowledge of the mathematical and natural sciences gained by study,
experience and practice is applied with judgement to develop ways to utilize, economically, the
materials and forces of nature for the benefit of mankind [Accreditation Board for Engineering and
Technology, 1996]
Software Requirements Specification for Healthcare Maintenance System Page 8

Appendix B: Analysis Models

Common questions

Powered by AI

Design and implementation constraints in the Healthcare Maintenance System can significantly impact overall functionality by limiting the system's flexibility and adaptability. For instance, constraints could restrict timely data access by doctors when viewing or updating patient records, potentially affecting patient care . Additionally, these constraints might limit the system's ability to incorporate changes promptly, like adopting new technologies or features, thus hindering system upgrades and its ability to effectively manage hospital activities . Properly addressing these constraints is crucial for maintaining system efficiency and meeting evolving healthcare needs.

The primary user classes of the Healthcare Maintenance System include customers/patients, doctors, chemists, physicians, web developers, and other healthcare staff such as nurses . The system caters to each class by providing features tailored to their roles, such as allowing doctors to view patient records immediately for better patient care, web developers to build and maintain the website effectively, and patients to easily access their treatment details . The user-friendly interface ensures that even users with basic computer skills can operate the system efficiently .

The use of modular design in the Healthcare Maintenance System enhances user documentation and maintenance by dividing the system into independent modules, each with distinct significance and function . This organization facilitates easier updates, as each module can be individually modified without affecting the entire system. It improves documentation by enabling focused, clear instructions for specific system parts, thus simplifying user understanding and troubleshooting. Furthermore, modularity supports the efficient pinpointing and resolution of system issues, enhancing overall system resilience and adaptability .

User feedback plays a crucial role in refining the Healthcare Maintenance System, as it supports diverse user classes such as doctors, patients, and healthcare staff. Feedback allows developers to identify areas for improvement, enhancing user interfaces and functionality based on real-world user experiences and needs . By incorporating suggestions and addressing issues raised by various user groups, the system can increase its usability and efficacy, ensuring it meets the specific requirements of each class. Continuous feedback loops facilitate ongoing optimization, leading to a more robust and user-friendly healthcare solution .

Safety measures in the Healthcare Maintenance System include options for cross-verification with doctors if there is any doubt about disease prediction. This is crucial as numerous diseases might share similar symptoms, which could lead to misdiagnosis . The system also recommends consulting with appointed doctors for accurate diagnosis during treatment, providing a safety net against incorrect predictions. By issuing digital certificates and cross-checking user information with doctors' evaluations, the system ensures reliability and accuracy in diagnosis .

The Healthcare Maintenance System streamlines the patient billing process by automating the calculation of bills based on various criteria such as room allocation, lab reports, treatment, and medicines taken . This automation speeds up the billing process while ensuring accuracy. The system considers health card facilities during billing, making the process comprehensive. It is designed to perform major functions like calculating bills quickly and simply, which contributes to the efficiency and accuracy of overall billing .

The Healthcare Maintenance System utilizes external interface requirements like user-friendly hardware and software interfaces to enhance user experience and system efficiency. Hardware interfaces require a Windows 10 OS, 1 TB hard disk, and 8 GB RAM to ensure smooth operations . The software interface employs HTML, CSS, and JavaScript for intuitive front-end design, facilitating ease of use. By integrating these interfaces, the system provides streamlined interactions through keyboards and mice, improving the overall operational workflow and contributing to an efficient user experience .

Critical assumptions and dependencies of the Healthcare Maintenance System include the reliance on a stable and high-speed internet connection for accessing the medical record repository and assuming users have the necessary hardware to interact with the system . These assumptions influence operations by dictating system accessibility and performance reliability. Without meeting these conditions, the system’s efficiency and functionality could be compromised, as users would face challenges in accessing and utilizing system features. Recognizing and planning for these dependencies are essential for ensuring seamless and effective system operations .

The Healthcare Maintenance System ensures secure handling of patient data by requiring proper authentication and issuing digital certificates to validate identity, often tied to prescriptions or medical diagnoses . Despite these measures, potential risks still involve incorrect authentication, which could lead to legal issues and breaches of confidentiality. These risks highlight the importance of robust security protocols within the system. Digital handling of sensitive data requires constant updates to security measures to address emerging threats and maintain data integrity .

The Healthcare Maintenance System's domain model outlines the complex relationships and interactions among system entities, thereby supporting its main goal of accurate disease prediction and efficient patient management. This model organizes processes such as symptom input, disease profile matching, and automated scheduling within cohesive use cases . It facilitates clear data flow and interaction sequences, ensuring that patient inputs yield accurate diagnostics and appointment setups. The structured domain model is vital for enabling precise predictions and maintaining a seamless patient care cycle, ultimately contributing to the system's efficacy .

You might also like