SlideShare a Scribd company logo
Mamoona Asma.
SESSION:2015 - 2017 | ALNOOREDUCATION COLLEGE HASILPUR
HOSPITAL ERP
SYSTEM
SOFTWARE REQUIREMENTS SPECIFICATION DOCUMENT
01-04-2017
HospitalERP System
ii
Revision History
Date Description Author Comments
Document Approval
The following Software Requirements Specification has been accepted and approved by the following:
Signature Printed Name Title Date
Dr. Supervisor, CSIT 21306
HospitalERP System
iii
Table of Contents
1. Introduction 1
1.1 Purpose 1
1.2 Scope 1
1.3 Definitions, Acronyms, and Abbreviations. 2
1.4 References 2
1.5 Overview 2
2. The Overall Description 3
2.1 Product Perspective 3
2.1.1 Operations 3
2.1.2 Site Adaptation Requirements 3
2.2 Product Function 3
2.3 User Characteristics 5
2.4 General Constraints 6
2.5 Assumptions and Dependencies 6
3. Specific Requirements 7
3.1 External Interface Requirements 7
3.1.1 System Interfaces 7
3.1.2 Interfaces 7
3.1.3 Hardware Interfaces 7
3.1.4 Software Interfaces 8
3.1.5 Communications Interfaces 8
3.2 Functional Requirements 8
3.2.1 Registration 8
3.2.2 Login 9
3.2.3 Appointment Module 9
3.2.4 ViewPatient Information 10
3.2.5 Pathology module 10
3.2.6 Prescribe Medicine 11
3.3.7 Paramedic services 11
3.3.8 Doctor module 12
3.3.9 Generate Report 12
3.2.10 Charge Fee 13
3.2.11 Billing and Maintenance module 13
3.3 Use Cases 14
3.3.1 Use Case: System 14
3.3.2 Use Case: System1 15
3.4 Non-Functional Requirements 16
3.5.1 Performance 16
3.5.2 Reliability 16
3.5.3 Availability 16
3.5.4 Security 16
HospitalERP System
iv
3.5.5 Maintainability 16
3.5.6 Portability 16
4. Analysis Models 17
4.1 Sequence Diagram 17
4.2 Data Flow Diagrams (DFD) 19
4.3 State-Transition Diagrams (STD) 20
HospitalERP System
SRS Document 1.0 Page 1 of 25 04/22/18f
1. Introduction
The introduction of SRS (Software Requirement specification document) provides the
overview of HOSPITAL ERP SYSTEM. This project is the best enterprise resource
management system for the hospital. The SRS is the practical specification of
requirement of HOSPITAL ERP SYSTEM. In this documentation two users
administrator and user , consist of patient details ,patient test prescription , precaution’s
and billing and report generation.
1.1 Purpose
The main purpose of this document is to describe all the specification of HOSPITAL
ERP SYSTEM. This document consist of maintaining and editing the patient details,
provides description of patient disease’s, precaution’s and all kinds of test of the patients,
report generation and billing. This project can be used in any HOSPITAL, CLINIC etc.
1.2 Scope
 The promote software product is the HOSPITAL ERP SYSTEM.
 This is useful to get the information about the patient and doctors. This system
is useful for any Hospital and Clinics. The pathological labs in any hospital
easily get the information of the patients and also stored the record of patients
for further used.
 Doctors also used the system to get the recent conditions of the patients Nurses
also used this system to interact with the patients and gives well care of the
patients.
 The past system and now days also paper work is used. The paper work is slow
and also the chance of data loss. The current system not provide the update
information of the patients in a reasonable timeframe, the doctor must pick the
round and see that are patients treat well or not?
 This system reduces over-time pay and increase the number of patients that
treated well and accurately.
 Functional and non-functional requirements are used in this system.
HospitalERP System
SRS Document 1.0 Page 2 of 25 04/22/18f
1.3 Definitions, Acronyms, and Abbreviations.
GUI Graphical User Interface
OPD Outdoor and Indoor Patients
OS Operating System
PC Personal Computers
DFD Data Flow Diagrams
ECG Electrocardiogram
ETU Emergency Tactical Unit
ID Identity
.
1.4 References
https://www.slideshare.net/pranild/hospital-management-system-slidshare
https://www.slideshare.net/kataria55/srs-for-hospital-management-
systemhttp://www.freestudentprojects.com/studentprojectreport/project-srs/srs-documentation-for-
hospital-management-system/
https://www.scribd.com/doc/60567651/Hospital-Management-System-SRS-and-UML-
Diagramshttp://www.dotnetfunda.com/articles/show/1052/sample-software-requirements-specification-
for-hospital-info-managemen
http://cssubjects.skoze.com/2013/02/24/hospital-management-system-hms-zohaib-shoket-110-bscs-2010/
https://www.academia.edu/28734143/HOSPITAL_MANAGEMENT_SYSTEM_Software_Requirement_
Specification?auto=download
1.5 Overview
This document is divided into four chapters. First chapter includes introduction to the application
as well as includes basic information of this document. Chapter two deals with the details related
to application design such as interfaces, software and hardware requirements. Chapter 3 includes
details about functional and non-functional requirements. Chapter 4 contains different types of
diagrams related to this application being developed.
HospitalERP System
SRS Document 1.0 Page 3 of 25 04/22/18f
2. The Overall Description
.
2.1 Product Perspective
This proposed system is self-sufficient product to replace the old paper work record
system. All records are easily updated and managed. Many participants are involved in this
hospital ERP system. The following subsections describe how the software operates inside
various constraints.
2.1.1 Operations
 Admin have access to whole system and he/she has complete knowledge of the
system. He/she has authority to add, delete, update or modify the system.
 Receptionist adds or delete of the details of patient that comes for treatment and
gives them the peculiarity.
 Doctors should also know the system and see the all appointments taken. Doctors
also view the patient records.
 Clinical Pathologist that examine blood, urine, bone marrows, ECG etc.
 Casual users can view the timing of the doctors and take appointments.
 Paramedic services are provided on the basis of emergency.
2.1.2 Site Adaptation Requirements
No specific requirements on site are required for this application.
2.2 Product Function
 OPD And Consolation Management
 Patient record
 Issuing number according to the doctor channeled
 Manage record with medical instruction
 Print bills of doctor chargers
 Employee and Salary Management
 Presence of employee
 Time table of consulting doctor
 Vacations
 Shares of doctors who sent patients for ECG ,BLOOD test etc
HospitalERP System
SRS Document 1.0 Page 4 of 25 04/22/18f
HospitalERP System
SRS Document 1.0 Page 5 of 25 04/22/18f
 Theater and Medical Ward Management
 Surgeon detail
 Surgery failure or success
 Patient complication and other detail
 Calculate bills and reports
 Emergency Transport Management
 Ambulance management
 Time management
 Billing calculation
 Emergency Treatment and Apparatus Management
 Emergency patient details
 Issue test reports
 Lab apparatus management
2.3 User Characteristics
 Admin
Admin is the user who interact whole system and manage all activities, so
that he is the most privileged user of the system.
Followings are the activities of Admin:
 Manage apparatus ,patient and employee
 Manage Ambulances
 Manage Doctors
 Manage Salaries
 Assign Resources
 Check out reports
 Receptionist
Users have only access to specific modules of the system according
the needs.
Following are activities of user:
 Monitor Patient details
 Monitor Patient Test details
 Ambulance reservation
HospitalERP System
SRS Document 1.0 Page 6 of 25 04/22/18f
 Monitor Patient updates
 Manage bills calculations
 Schedule management
 Patient record management
 Clinical Pathologist
Clinical Pathologist examines the patients.
Following are the activities of clinical Pathologist:
 Blood test
 Urine test
 Bone marrow test
 ECG
 Casual user
Casual users can view the timing of doctors and take appointments.
2.4 General Constraints
2.5 Assumptions and Dependencies
 All the data entered is free of syntax errors.
 This product interface is simple and easy to understand.
 Every user must have a valid id and password.
 System should be accessed only authorized user.
 Only the admin can delete and update records .
.
HospitalERP System
SRS Document 1.0 Page 7 of 25 04/22/18f
3. Specific Requirements
3.1 External Interface Requirements
3.1.1 System Interfaces
3.1.2 Interfaces
 A form for Admin login and he/she manage adds, delete or modify the
whole system. He/she also check out whole system.
 A login screen for user id and password and role (Admin, User) will be
provided. Access to different pages according to the different aspects of
user.
 A screen that shows the details of patients.
 A screen that created the patient id by the user and filled out all patient
necessary information.
 A screen that generated test reports of patients.
 A form that generated bill according to the Patients ID, hospital
charges and test chargers.
 A form for Pathologist that consist of patient test details and records.
 A form that allocate the ambulances for emergency.
3.1.3 Hardware Interfaces
 server
Processor: Intel/Pentium-(iii/iv or above)
Ram: 2MB or above
Hard disk: 40GB or above
Input devices: keyboard, Mouse
Output devices: Monitor, LED etc
 clients
Processor: Intel/Pentium-(iii/iv or above)
Ram: 2MB or above
Hard disk: 40GB or above
Input devices: keyboard, Mouse
Output devices: Monitor, LED etc.
HospitalERP System
SRS Document 1.0 Page 8 of 25 04/22/18f
3.1.4 Software Interfaces
 Window 8 or above
 HTML
 CSS
 PHP
 MY SQL
 JAVA SCRIPT
 WAMP SERVER
 ADOBEDREAMVIEWER
3.1.4.1 Microsoft SQL Server
MYSQL will be usedtostore recordsin database..
3.1.5 Communications Interfaces
 Sender and receivers can communicate through internet. Internet is the main part of
this application.
 TCP/IP and HTTP protocol internet service providers are used to access and share
the information through internet.
3.2 Functional Requirements
Here Registration, login module, Appointment module, View Patient Information,
Pathology module, Doctors module, Prescribe Medicine, Paramedic services, Charge Fee, Login
Generate Report, billing report.
3.2.1 Registration
3.2.1.1 Introduction
The user signup into the front end and create the account.
3.2.1.2 Inputs
The user enters their NAME,PHONE NUMBER, ADDRESS, and other information.
3.2.1.3 Processing
The information is stored in the database.
3.2.1.4 Outputs
The user/patient account is created.
3.2.1.5 Error Handling
HospitalERP System
SRS Document 1.0 Page 9 of 25 04/22/18f
If record is not stored successfully .Then reentered the record.
3.2.2 Login
3.2.2.1 Introduction
The system can only access by the authority user (Admin/ user).
3.2.2.2 Inputs
The user enters their id and password.
3.2.2.3 Processing
Record is checked in the database.
3.2.2.4 Outputs
User access the specific form that they want.
3.2.2.5 Error Handling
Record not found.
3.2.3 Appointment Module
3.2.3.1 Introduction
Receptionist is the one who is dealing with the Patient Appointment Module.
3.2.3.2 Input
The Appointment Module is allowed the staff to add the appointment and delete or cancel
the appointment if patient is asked.
3.2.3.3 Processing
The record is checked in the database.
3.2.3.4 Output
Patient assigns the appointment.
3.2.3.5 Error Handling
If appointments are not assigned to Patient then request again.
HospitalERP System
SRS Document 1.0 Page 10 of 25 04/22/18f
3.2.4 View Patient Information
3.2.4.1 Introduction
It keeps all details of the Indoor-Patient and Outdoor -Patient .Patient ID. NAME,
ADDRESS, ADMITTED DATE and other information are entered inthe form and store
for further used.
3.2.4.2 Input
Indoor-Patient admitted before visiting the hospital and Outdoor-Patient are visited the
hospital earlier.
3.2.4.3 Processing
Records are checked in the database.
3.2.4.4 Output
Indoor and outdoor patients are viewed.
3.2.4.5 Error Handling
The data are not stored in the database.
3.2.5 Pathology module
3.3.5.1 Introduction
In this module reports are generated in the specific pathology lab of the HOSPITAL.
3.3.5.2 Input
Lab report inputs as provided by lab attendant.
3.3.5.3 Processing
Provided details as mentioned on the report generated by lab attendant will be stored into
the database.
3.3.5.4 Output
A message will be displayed to the user in case of successful entry of record and also in
case if records are not stored into the database.
3.3.5.5 Error Handling
In case of any error, user will be redirected to Pathology Module to refill the form and
submit information again.
HospitalERP System
SRS Document 1.0 Page 11 of 25 04/22/18f
3.2.6 Prescribe Medicine
3.3.6.1 Introduction
This module will deal with the information provided by doctor when diagnosing a patient
and prescribe medicine. An interface will be provided to enter the prescription for a patient along
with any additional diagnostics made such as BP, Fever etc.
3.3.6.2 Input
Doctor after examining a patient will prescribe list of medicines containing medicine
name, dosage, and number of days for which that medicine will be used.
3.3.6.3 Processing
Medicines prescribed by the doctor will be added to database for that patient.
3.3.6.4 Output
User of application will be informed via a message in case of successful of unsuccessful
insertion of records.
3.3.6.5 Error Handling
In case any error; user will be redirected to Prescribe Medicine page.
3.3.7 Paramedic services
3.3.7.1 Introduction
This module will deal if any emergency is occurred; provided the ambulance to patients.
3.3.7.2 Input
Enter the emergency patient information.
3.3.7.3 Processing
Ambulance provided by the staff is stored in the database.
3.3.7.4 Output
A user of application gives the paramedic services.
3.3.7.5 Error Handling
In case of any error; user will be redirected to paramedic services page.
HospitalERP System
SRS Document 1.0 Page 12 of 25 04/22/18f
3.3.8 Doctor module
3.3.8.1 Introduction
Doctors can check appointment taken by patients; view patients test reports and also view the
salary and billing reports.
3.3.8.2 Input
Doctors login to the website. He/she view the patient appointment list, old records, prescription,
payment details and monthly salary.
3.3.8.3 Processing
Records are checked in the database.
3.3.8.4 Output
Doctors can view old records and manage their fee charges.
3.3.8.5 Error Handling
In case of any error; user will be redirected to doctor module page
3.3.9 Generate Report
3.3.9.1 Introduction
In this module the report is generated by the staff. This report consist of the patient information
(id, name, phone number, ward number)
3.3.9.2 Input
The hospital staff login to the page and edit or view the patient report.
3.3.9.3 Processing
The records are checked in the database.
3.3.9.4 Output
In case of any error; user will be redirected to generate report page.
HospitalERP System
SRS Document 1.0 Page 13 of 25 04/22/18f
3.2.10 Charge Fee
3.3.10.1 Introduction
In this module the user can view the charge fee of DOCTORS that are available in
Hospital.
3.3.10.2 Input
Users are login into the website to view the charge fee of the doctors.
3.3.10.2 Processing
Records are checked in the database.
3.3.10.3 Output
Users view the charge fee of the doctors and take appointment.
3.3.10.4 Error Handling
In case of any error; user will be redirected to the charge fee page.
3.2.11 Billing and Maintenance module
3.3.11.1 Introduction
In this module calculate the bills of the patient (outdoor and indoor) and receptionist enter
charge fee, pathology lab fee. The system automatically generated the doctor’s salary and
monthly income and expenses.
3.3.11.2 Input
Users are login into the website to calculate the bills and view the old record.
3.3.11.2 Processing
Records are checked in the database.
3.3.11.3 Output
Bills and income of the doctors are generated.
3.3.11.4 Error Handling
In case of any error, user will be redirected to the billing and maintenance page.
HospitalERP System
SRS Document 1.0 Page 14 of 25 04/22/18f
3.3 Use Cases
3.3.1 Use Case: System
HospitalERP System
SRS Document 1.0 Page 15 of 25 04/22/18f
3.3.2 Use Case: System1
HospitalERP System
SRS Document 1.0 Page 16 of 25 04/22/18f
3.4 Non-Functional Requirements
3.5.1 Performance
 The system gives response within 60 seconds after checking the patients details.
 The system supports 800 peoples at a time.
 User interface screen gives response within 2 seconds.
 The system conforms to the Microsoft accessibility.
3.5.2 Reliability
 The user must be enter valid information; avoidance of incorrect storage of
records.
 There should be an additional server for backup data if server is down; so that the
system is continuous running.
 In case of any error occurred; the error message should be prompt to the user.
3.5.3 Availability
 The system shall be available all the time.
3.5.4 Security
 The system should be secure for the use of unauthorized access of the user.
 The system must provide the privacy for Patient information.
 The system should access only by authorized user .
3.5.5 Maintainability
 The maintenance ability of the system modifies records and fix problems if
occurred.
3.5.6 Portability
 The system should be installed in any PC supports windows OS.
HospitalERP System
SRS Document 1.0 Page 17 of 25 04/22/18f
4. Analysis Models
4.1 Sequence Diagram
HospitalERP System
SRS Document 1.0 Page 18 of 25 04/22/18f
HospitalERP System
SRS Document 1.0 Page 19 of 25 04/22/18f
4.2 Data Flow Diagrams (DFD)
HospitalERP System
SRS Document 1.0 Page 20 of 25 04/22/18f
4.3 State-Transition Diagrams (STD)
HospitalERP System
SRS Document 1.0 Page 21 of 25 04/22/18f

More Related Content

PPTX
Structural equation modeling in amos
PDF
Structural Equation Modeling (SEM) with AMOS
DOCX
Food donation project report II
PPTX
Knowledge Work System
PPTX
FATTY LIVER
PPTX
Head injury management lecture.ppt (1)
PPTX
Awareness SNI ISO 21001:2018 Sistem Manajemen untuk Organisasi Pendidikan
PPT
blood transfusion ppt
Structural equation modeling in amos
Structural Equation Modeling (SEM) with AMOS
Food donation project report II
Knowledge Work System
FATTY LIVER
Head injury management lecture.ppt (1)
Awareness SNI ISO 21001:2018 Sistem Manajemen untuk Organisasi Pendidikan
blood transfusion ppt

What's hot (20)

PPTX
Hospital erp software
PPT
Hospital Management System
PPSX
Hospital Management System-out patient Detail
PPT
Healthcare copy
PPTX
Hospital Information System
PPTX
[PPT] Hospital management system - Quanta-his
PPTX
HOSPITAL ERP - ABSOLINSOFT
DOC
Design and implementation of a hospital management system
PPTX
hospital management system
PPT
MIS Role in Production
PPTX
Hospital managment system
PPTX
hospital management System
PPTX
Hospital management system
PPT
Hospital erp( ERP System for Hospitals ) an opensource erp system
PPT
"Hospital Management"
PPTX
Hospital management
PDF
Hospital management-system
PPTX
Hospital Management System
PPT
Hospital information system
DOCX
Hospital management system
Hospital erp software
Hospital Management System
Hospital Management System-out patient Detail
Healthcare copy
Hospital Information System
[PPT] Hospital management system - Quanta-his
HOSPITAL ERP - ABSOLINSOFT
Design and implementation of a hospital management system
hospital management system
MIS Role in Production
Hospital managment system
hospital management System
Hospital management system
Hospital erp( ERP System for Hospitals ) an opensource erp system
"Hospital Management"
Hospital management
Hospital management-system
Hospital Management System
Hospital information system
Hospital management system
Ad

Similar to Hospital erp system (20)

DOCX
SRS for Hospital Management System
DOC
Srs hospital management
PDF
Electronic Medical Regulation
PDF
Hospital Management System Project Report
PDF
Hospital Management System Project
DOCX
Hospitalmanagementsystemproject 140513065037-phpapp02
PDF
HOSPITAL MANAGEMENT SYSTEM PROJECT
DOCX
Hospital management system project
PDF
Systems Analysis and Design for Post Treatment Healthcare App
PPTX
Hosiptal-MS-PPT-zl64ci.pptx
DOC
Hospital management system report
DOCX
Hostpital management system(srs)
DOCX
Physiotherapy clinical system
PDF
IRJET- An Android Application for Electronic Health Record System
PDF
IRJET- An Android Application for Electronic Health Record System
PPTX
Hospital presentation
PPT
Sample - Software Requirements Specification for Hospital Info Management System
DOCX
PDF
HOSPITAL MANAGEMENT SYSTEM: FEATURES, REQUIREMENTS AND BENEFITS
DOCX
Hospital mangement system report file
SRS for Hospital Management System
Srs hospital management
Electronic Medical Regulation
Hospital Management System Project Report
Hospital Management System Project
Hospitalmanagementsystemproject 140513065037-phpapp02
HOSPITAL MANAGEMENT SYSTEM PROJECT
Hospital management system project
Systems Analysis and Design for Post Treatment Healthcare App
Hosiptal-MS-PPT-zl64ci.pptx
Hospital management system report
Hostpital management system(srs)
Physiotherapy clinical system
IRJET- An Android Application for Electronic Health Record System
IRJET- An Android Application for Electronic Health Record System
Hospital presentation
Sample - Software Requirements Specification for Hospital Info Management System
HOSPITAL MANAGEMENT SYSTEM: FEATURES, REQUIREMENTS AND BENEFITS
Hospital mangement system report file
Ad

Recently uploaded (20)

PPTX
Pharmacology of Heart Failure /Pharmacotherapy of CHF
PPTX
The Healthy Child – Unit II | Child Health Nursing I | B.Sc Nursing 5th Semester
PDF
Saundersa Comprehensive Review for the NCLEX-RN Examination.pdf
PPTX
UNDER FIVE CLINICS OR WELL BABY CLINICS.pptx
PPTX
human mycosis Human fungal infections are called human mycosis..pptx
PPTX
Microbial diseases, their pathogenesis and prophylaxis
PPTX
school management -TNTEU- B.Ed., Semester II Unit 1.pptx
PPTX
Cardiovascular Pharmacology for pharmacy students.pptx
PDF
STATICS OF THE RIGID BODIES Hibbelers.pdf
PPTX
Renaissance Architecture: A Journey from Faith to Humanism
PDF
Chapter 2 Heredity, Prenatal Development, and Birth.pdf
PPTX
Open Quiz Monsoon Mind Game Prelims.pptx
PDF
The Final Stretch: How to Release a Game and Not Die in the Process.
PPTX
COMPUTERS AS DATA ANALYSIS IN PRECLINICAL DEVELOPMENT.pptx
PDF
Mark Klimek Lecture Notes_240423 revision books _173037.pdf
PDF
The Lost Whites of Pakistan by Jahanzaib Mughal.pdf
PDF
PSYCHOLOGY IN EDUCATION.pdf ( nice pdf ...)
PDF
Anesthesia in Laparoscopic Surgery in India
PDF
01-Introduction-to-Information-Management.pdf
PDF
O7-L3 Supply Chain Operations - ICLT Program
Pharmacology of Heart Failure /Pharmacotherapy of CHF
The Healthy Child – Unit II | Child Health Nursing I | B.Sc Nursing 5th Semester
Saundersa Comprehensive Review for the NCLEX-RN Examination.pdf
UNDER FIVE CLINICS OR WELL BABY CLINICS.pptx
human mycosis Human fungal infections are called human mycosis..pptx
Microbial diseases, their pathogenesis and prophylaxis
school management -TNTEU- B.Ed., Semester II Unit 1.pptx
Cardiovascular Pharmacology for pharmacy students.pptx
STATICS OF THE RIGID BODIES Hibbelers.pdf
Renaissance Architecture: A Journey from Faith to Humanism
Chapter 2 Heredity, Prenatal Development, and Birth.pdf
Open Quiz Monsoon Mind Game Prelims.pptx
The Final Stretch: How to Release a Game and Not Die in the Process.
COMPUTERS AS DATA ANALYSIS IN PRECLINICAL DEVELOPMENT.pptx
Mark Klimek Lecture Notes_240423 revision books _173037.pdf
The Lost Whites of Pakistan by Jahanzaib Mughal.pdf
PSYCHOLOGY IN EDUCATION.pdf ( nice pdf ...)
Anesthesia in Laparoscopic Surgery in India
01-Introduction-to-Information-Management.pdf
O7-L3 Supply Chain Operations - ICLT Program

Hospital erp system

  • 1. Mamoona Asma. SESSION:2015 - 2017 | ALNOOREDUCATION COLLEGE HASILPUR HOSPITAL ERP SYSTEM SOFTWARE REQUIREMENTS SPECIFICATION DOCUMENT 01-04-2017
  • 2. HospitalERP System ii Revision History Date Description Author Comments Document Approval The following Software Requirements Specification has been accepted and approved by the following: Signature Printed Name Title Date Dr. Supervisor, CSIT 21306
  • 3. HospitalERP System iii Table of Contents 1. Introduction 1 1.1 Purpose 1 1.2 Scope 1 1.3 Definitions, Acronyms, and Abbreviations. 2 1.4 References 2 1.5 Overview 2 2. The Overall Description 3 2.1 Product Perspective 3 2.1.1 Operations 3 2.1.2 Site Adaptation Requirements 3 2.2 Product Function 3 2.3 User Characteristics 5 2.4 General Constraints 6 2.5 Assumptions and Dependencies 6 3. Specific Requirements 7 3.1 External Interface Requirements 7 3.1.1 System Interfaces 7 3.1.2 Interfaces 7 3.1.3 Hardware Interfaces 7 3.1.4 Software Interfaces 8 3.1.5 Communications Interfaces 8 3.2 Functional Requirements 8 3.2.1 Registration 8 3.2.2 Login 9 3.2.3 Appointment Module 9 3.2.4 ViewPatient Information 10 3.2.5 Pathology module 10 3.2.6 Prescribe Medicine 11 3.3.7 Paramedic services 11 3.3.8 Doctor module 12 3.3.9 Generate Report 12 3.2.10 Charge Fee 13 3.2.11 Billing and Maintenance module 13 3.3 Use Cases 14 3.3.1 Use Case: System 14 3.3.2 Use Case: System1 15 3.4 Non-Functional Requirements 16 3.5.1 Performance 16 3.5.2 Reliability 16 3.5.3 Availability 16 3.5.4 Security 16
  • 4. HospitalERP System iv 3.5.5 Maintainability 16 3.5.6 Portability 16 4. Analysis Models 17 4.1 Sequence Diagram 17 4.2 Data Flow Diagrams (DFD) 19 4.3 State-Transition Diagrams (STD) 20
  • 5. HospitalERP System SRS Document 1.0 Page 1 of 25 04/22/18f 1. Introduction The introduction of SRS (Software Requirement specification document) provides the overview of HOSPITAL ERP SYSTEM. This project is the best enterprise resource management system for the hospital. The SRS is the practical specification of requirement of HOSPITAL ERP SYSTEM. In this documentation two users administrator and user , consist of patient details ,patient test prescription , precaution’s and billing and report generation. 1.1 Purpose The main purpose of this document is to describe all the specification of HOSPITAL ERP SYSTEM. This document consist of maintaining and editing the patient details, provides description of patient disease’s, precaution’s and all kinds of test of the patients, report generation and billing. This project can be used in any HOSPITAL, CLINIC etc. 1.2 Scope  The promote software product is the HOSPITAL ERP SYSTEM.  This is useful to get the information about the patient and doctors. This system is useful for any Hospital and Clinics. The pathological labs in any hospital easily get the information of the patients and also stored the record of patients for further used.  Doctors also used the system to get the recent conditions of the patients Nurses also used this system to interact with the patients and gives well care of the patients.  The past system and now days also paper work is used. The paper work is slow and also the chance of data loss. The current system not provide the update information of the patients in a reasonable timeframe, the doctor must pick the round and see that are patients treat well or not?  This system reduces over-time pay and increase the number of patients that treated well and accurately.  Functional and non-functional requirements are used in this system.
  • 6. HospitalERP System SRS Document 1.0 Page 2 of 25 04/22/18f 1.3 Definitions, Acronyms, and Abbreviations. GUI Graphical User Interface OPD Outdoor and Indoor Patients OS Operating System PC Personal Computers DFD Data Flow Diagrams ECG Electrocardiogram ETU Emergency Tactical Unit ID Identity . 1.4 References https://www.slideshare.net/pranild/hospital-management-system-slidshare https://www.slideshare.net/kataria55/srs-for-hospital-management- systemhttp://www.freestudentprojects.com/studentprojectreport/project-srs/srs-documentation-for- hospital-management-system/ https://www.scribd.com/doc/60567651/Hospital-Management-System-SRS-and-UML- Diagramshttp://www.dotnetfunda.com/articles/show/1052/sample-software-requirements-specification- for-hospital-info-managemen http://cssubjects.skoze.com/2013/02/24/hospital-management-system-hms-zohaib-shoket-110-bscs-2010/ https://www.academia.edu/28734143/HOSPITAL_MANAGEMENT_SYSTEM_Software_Requirement_ Specification?auto=download 1.5 Overview This document is divided into four chapters. First chapter includes introduction to the application as well as includes basic information of this document. Chapter two deals with the details related to application design such as interfaces, software and hardware requirements. Chapter 3 includes details about functional and non-functional requirements. Chapter 4 contains different types of diagrams related to this application being developed.
  • 7. HospitalERP System SRS Document 1.0 Page 3 of 25 04/22/18f 2. The Overall Description . 2.1 Product Perspective This proposed system is self-sufficient product to replace the old paper work record system. All records are easily updated and managed. Many participants are involved in this hospital ERP system. The following subsections describe how the software operates inside various constraints. 2.1.1 Operations  Admin have access to whole system and he/she has complete knowledge of the system. He/she has authority to add, delete, update or modify the system.  Receptionist adds or delete of the details of patient that comes for treatment and gives them the peculiarity.  Doctors should also know the system and see the all appointments taken. Doctors also view the patient records.  Clinical Pathologist that examine blood, urine, bone marrows, ECG etc.  Casual users can view the timing of the doctors and take appointments.  Paramedic services are provided on the basis of emergency. 2.1.2 Site Adaptation Requirements No specific requirements on site are required for this application. 2.2 Product Function  OPD And Consolation Management  Patient record  Issuing number according to the doctor channeled  Manage record with medical instruction  Print bills of doctor chargers  Employee and Salary Management  Presence of employee  Time table of consulting doctor  Vacations  Shares of doctors who sent patients for ECG ,BLOOD test etc
  • 8. HospitalERP System SRS Document 1.0 Page 4 of 25 04/22/18f
  • 9. HospitalERP System SRS Document 1.0 Page 5 of 25 04/22/18f  Theater and Medical Ward Management  Surgeon detail  Surgery failure or success  Patient complication and other detail  Calculate bills and reports  Emergency Transport Management  Ambulance management  Time management  Billing calculation  Emergency Treatment and Apparatus Management  Emergency patient details  Issue test reports  Lab apparatus management 2.3 User Characteristics  Admin Admin is the user who interact whole system and manage all activities, so that he is the most privileged user of the system. Followings are the activities of Admin:  Manage apparatus ,patient and employee  Manage Ambulances  Manage Doctors  Manage Salaries  Assign Resources  Check out reports  Receptionist Users have only access to specific modules of the system according the needs. Following are activities of user:  Monitor Patient details  Monitor Patient Test details  Ambulance reservation
  • 10. HospitalERP System SRS Document 1.0 Page 6 of 25 04/22/18f  Monitor Patient updates  Manage bills calculations  Schedule management  Patient record management  Clinical Pathologist Clinical Pathologist examines the patients. Following are the activities of clinical Pathologist:  Blood test  Urine test  Bone marrow test  ECG  Casual user Casual users can view the timing of doctors and take appointments. 2.4 General Constraints 2.5 Assumptions and Dependencies  All the data entered is free of syntax errors.  This product interface is simple and easy to understand.  Every user must have a valid id and password.  System should be accessed only authorized user.  Only the admin can delete and update records . .
  • 11. HospitalERP System SRS Document 1.0 Page 7 of 25 04/22/18f 3. Specific Requirements 3.1 External Interface Requirements 3.1.1 System Interfaces 3.1.2 Interfaces  A form for Admin login and he/she manage adds, delete or modify the whole system. He/she also check out whole system.  A login screen for user id and password and role (Admin, User) will be provided. Access to different pages according to the different aspects of user.  A screen that shows the details of patients.  A screen that created the patient id by the user and filled out all patient necessary information.  A screen that generated test reports of patients.  A form that generated bill according to the Patients ID, hospital charges and test chargers.  A form for Pathologist that consist of patient test details and records.  A form that allocate the ambulances for emergency. 3.1.3 Hardware Interfaces  server Processor: Intel/Pentium-(iii/iv or above) Ram: 2MB or above Hard disk: 40GB or above Input devices: keyboard, Mouse Output devices: Monitor, LED etc  clients Processor: Intel/Pentium-(iii/iv or above) Ram: 2MB or above Hard disk: 40GB or above Input devices: keyboard, Mouse Output devices: Monitor, LED etc.
  • 12. HospitalERP System SRS Document 1.0 Page 8 of 25 04/22/18f 3.1.4 Software Interfaces  Window 8 or above  HTML  CSS  PHP  MY SQL  JAVA SCRIPT  WAMP SERVER  ADOBEDREAMVIEWER 3.1.4.1 Microsoft SQL Server MYSQL will be usedtostore recordsin database.. 3.1.5 Communications Interfaces  Sender and receivers can communicate through internet. Internet is the main part of this application.  TCP/IP and HTTP protocol internet service providers are used to access and share the information through internet. 3.2 Functional Requirements Here Registration, login module, Appointment module, View Patient Information, Pathology module, Doctors module, Prescribe Medicine, Paramedic services, Charge Fee, Login Generate Report, billing report. 3.2.1 Registration 3.2.1.1 Introduction The user signup into the front end and create the account. 3.2.1.2 Inputs The user enters their NAME,PHONE NUMBER, ADDRESS, and other information. 3.2.1.3 Processing The information is stored in the database. 3.2.1.4 Outputs The user/patient account is created. 3.2.1.5 Error Handling
  • 13. HospitalERP System SRS Document 1.0 Page 9 of 25 04/22/18f If record is not stored successfully .Then reentered the record. 3.2.2 Login 3.2.2.1 Introduction The system can only access by the authority user (Admin/ user). 3.2.2.2 Inputs The user enters their id and password. 3.2.2.3 Processing Record is checked in the database. 3.2.2.4 Outputs User access the specific form that they want. 3.2.2.5 Error Handling Record not found. 3.2.3 Appointment Module 3.2.3.1 Introduction Receptionist is the one who is dealing with the Patient Appointment Module. 3.2.3.2 Input The Appointment Module is allowed the staff to add the appointment and delete or cancel the appointment if patient is asked. 3.2.3.3 Processing The record is checked in the database. 3.2.3.4 Output Patient assigns the appointment. 3.2.3.5 Error Handling If appointments are not assigned to Patient then request again.
  • 14. HospitalERP System SRS Document 1.0 Page 10 of 25 04/22/18f 3.2.4 View Patient Information 3.2.4.1 Introduction It keeps all details of the Indoor-Patient and Outdoor -Patient .Patient ID. NAME, ADDRESS, ADMITTED DATE and other information are entered inthe form and store for further used. 3.2.4.2 Input Indoor-Patient admitted before visiting the hospital and Outdoor-Patient are visited the hospital earlier. 3.2.4.3 Processing Records are checked in the database. 3.2.4.4 Output Indoor and outdoor patients are viewed. 3.2.4.5 Error Handling The data are not stored in the database. 3.2.5 Pathology module 3.3.5.1 Introduction In this module reports are generated in the specific pathology lab of the HOSPITAL. 3.3.5.2 Input Lab report inputs as provided by lab attendant. 3.3.5.3 Processing Provided details as mentioned on the report generated by lab attendant will be stored into the database. 3.3.5.4 Output A message will be displayed to the user in case of successful entry of record and also in case if records are not stored into the database. 3.3.5.5 Error Handling In case of any error, user will be redirected to Pathology Module to refill the form and submit information again.
  • 15. HospitalERP System SRS Document 1.0 Page 11 of 25 04/22/18f 3.2.6 Prescribe Medicine 3.3.6.1 Introduction This module will deal with the information provided by doctor when diagnosing a patient and prescribe medicine. An interface will be provided to enter the prescription for a patient along with any additional diagnostics made such as BP, Fever etc. 3.3.6.2 Input Doctor after examining a patient will prescribe list of medicines containing medicine name, dosage, and number of days for which that medicine will be used. 3.3.6.3 Processing Medicines prescribed by the doctor will be added to database for that patient. 3.3.6.4 Output User of application will be informed via a message in case of successful of unsuccessful insertion of records. 3.3.6.5 Error Handling In case any error; user will be redirected to Prescribe Medicine page. 3.3.7 Paramedic services 3.3.7.1 Introduction This module will deal if any emergency is occurred; provided the ambulance to patients. 3.3.7.2 Input Enter the emergency patient information. 3.3.7.3 Processing Ambulance provided by the staff is stored in the database. 3.3.7.4 Output A user of application gives the paramedic services. 3.3.7.5 Error Handling In case of any error; user will be redirected to paramedic services page.
  • 16. HospitalERP System SRS Document 1.0 Page 12 of 25 04/22/18f 3.3.8 Doctor module 3.3.8.1 Introduction Doctors can check appointment taken by patients; view patients test reports and also view the salary and billing reports. 3.3.8.2 Input Doctors login to the website. He/she view the patient appointment list, old records, prescription, payment details and monthly salary. 3.3.8.3 Processing Records are checked in the database. 3.3.8.4 Output Doctors can view old records and manage their fee charges. 3.3.8.5 Error Handling In case of any error; user will be redirected to doctor module page 3.3.9 Generate Report 3.3.9.1 Introduction In this module the report is generated by the staff. This report consist of the patient information (id, name, phone number, ward number) 3.3.9.2 Input The hospital staff login to the page and edit or view the patient report. 3.3.9.3 Processing The records are checked in the database. 3.3.9.4 Output In case of any error; user will be redirected to generate report page.
  • 17. HospitalERP System SRS Document 1.0 Page 13 of 25 04/22/18f 3.2.10 Charge Fee 3.3.10.1 Introduction In this module the user can view the charge fee of DOCTORS that are available in Hospital. 3.3.10.2 Input Users are login into the website to view the charge fee of the doctors. 3.3.10.2 Processing Records are checked in the database. 3.3.10.3 Output Users view the charge fee of the doctors and take appointment. 3.3.10.4 Error Handling In case of any error; user will be redirected to the charge fee page. 3.2.11 Billing and Maintenance module 3.3.11.1 Introduction In this module calculate the bills of the patient (outdoor and indoor) and receptionist enter charge fee, pathology lab fee. The system automatically generated the doctor’s salary and monthly income and expenses. 3.3.11.2 Input Users are login into the website to calculate the bills and view the old record. 3.3.11.2 Processing Records are checked in the database. 3.3.11.3 Output Bills and income of the doctors are generated. 3.3.11.4 Error Handling In case of any error, user will be redirected to the billing and maintenance page.
  • 18. HospitalERP System SRS Document 1.0 Page 14 of 25 04/22/18f 3.3 Use Cases 3.3.1 Use Case: System
  • 19. HospitalERP System SRS Document 1.0 Page 15 of 25 04/22/18f 3.3.2 Use Case: System1
  • 20. HospitalERP System SRS Document 1.0 Page 16 of 25 04/22/18f 3.4 Non-Functional Requirements 3.5.1 Performance  The system gives response within 60 seconds after checking the patients details.  The system supports 800 peoples at a time.  User interface screen gives response within 2 seconds.  The system conforms to the Microsoft accessibility. 3.5.2 Reliability  The user must be enter valid information; avoidance of incorrect storage of records.  There should be an additional server for backup data if server is down; so that the system is continuous running.  In case of any error occurred; the error message should be prompt to the user. 3.5.3 Availability  The system shall be available all the time. 3.5.4 Security  The system should be secure for the use of unauthorized access of the user.  The system must provide the privacy for Patient information.  The system should access only by authorized user . 3.5.5 Maintainability  The maintenance ability of the system modifies records and fix problems if occurred. 3.5.6 Portability  The system should be installed in any PC supports windows OS.
  • 21. HospitalERP System SRS Document 1.0 Page 17 of 25 04/22/18f 4. Analysis Models 4.1 Sequence Diagram
  • 22. HospitalERP System SRS Document 1.0 Page 18 of 25 04/22/18f
  • 23. HospitalERP System SRS Document 1.0 Page 19 of 25 04/22/18f 4.2 Data Flow Diagrams (DFD)
  • 24. HospitalERP System SRS Document 1.0 Page 20 of 25 04/22/18f 4.3 State-Transition Diagrams (STD)
  • 25. HospitalERP System SRS Document 1.0 Page 21 of 25 04/22/18f