Hospital Management System SRS for software
1,566 views
37 slides
Feb 26, 2024
Slide 1 of 37
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
About This Presentation
SRS of Hospital Mgmt System
Slide Content
Hospital Management System
Submitted By
Mahmud Islam
1834902057
Anowar Jahid
1834902059
A project report submitted in partial fulfillment of the requirements for the
Degree of Bachelor of Science in Computer Science and Engineering
Supervised By
Shahadat Hossain
Lecturer
Department of CSE
City University
CITY UNIVERSITY
DHAKA, BANGLADESH
July 2022
Submitted By
Mahmud Islam
1834902057
Anowar Jahid
1834902059
A project report submitted in partial fulfillment of the requirements for the
Degree of Bachelor of Science in Computer Science and Engineering
Supervised By
Shahadat Hossain
Lecturer
Department of CSE
City University
CITY UNIVERSITY
DHAKA, BANGLADESH
July 2022
Page | I
DECLARATION
I hereby declare that, this project titled ‘‘Hospital Management System” is original record was
done by me under the supervision of, Shahadat Hossain Lecturer, Department of CSE at CITY
UNIVERSITY, Dhaka, affiliated to the partial fulfillment of requirement for the award of degree
of Bachelor of Computer Science and Engineering during the period of 2018- 2022 at CITY
UNIVERSITY and also we state that this project has not been submitted anywhere in the partial
fulfillment for any degree of this or any other University.
Submitted To:
Shahadat Hossain
Supervisor
Lecturer
Department of Computer Science & Engineering
City University, Dhaka, Bangladesh.
Submitted By:
Mahmud Islam
ID: 1834902057
Batch: 49
th
(eve)
Department of Computer Science & Engineering
City University, Dhaka, Bangladesh.
Anowar Jahid
ID: 1834902059
Batch: 49
th
(eve)
Department of Computer Science & Engineering
City University, Dhaka, Bangladesh.
DECLARATION
I hereby declare that, this project titled ‘‘Hospital Management System” is original record was
done by me under the supervision of, Shahadat Hossain Lecturer, Department of CSE at CITY
UNIVERSITY, Dhaka, affiliated to the partial fulfillment of requirement for the award of degree
of Bachelor of Computer Science and Engineering during the period of 2018- 2022 at CITY
UNIVERSITY and also we state that this project has not been submitted anywhere in the partial
fulfillment for any degree of this or any other University.
Submitted To:
Shahadat Hossain
Supervisor
Lecturer
Department of Computer Science & Engineering
City University, Dhaka, Bangladesh.
Submitted By:
Mahmud Islam
ID: 1834902057
Batch: 49
th
(eve)
Department of Computer Science & Engineering
City University, Dhaka, Bangladesh.
Anowar Jahid
ID: 1834902059
Batch: 49
th
(eve)
Department of Computer Science & Engineering
City University, Dhaka, Bangladesh.
Page | II
ACKNOWLEDGEMENT
Project development is not an easy task. It requires cooperation and help of various people. It
always happens that word run out when we are really thankful and sincerely want to inspire our
feeling of gratitude towards the one when helped in the completion of the project.
We are deeply indebted to my supervisor Shahadat Hossain Lecturer and of Department of
Computer Science & Engineering, City University, Dhaka, Bangladesh. Without his help.
guidance, sympathetic co-operation, stimulating suggestions and encouragement, the planning and
development of this project would be very difficult for us.
Our special thanks go to the Head of the Department of CSE, Md. Safaet Hossain, who had given
us the permission and encouraged us to go ahead. We are bound to the Honorable Dean of
Department of Science Faculty, Prof. Dr. Engr. Md. Huamaun Kabir, for his endless support.
I am very grateful to all my faculty teachers who gave me their valuable guides to complete my
graduation. I am also very grateful to all those people who have helped me to complete my project.
Mahmud Islam
ID: 1834902057
Batch: 49
th
(eve)
Department of Computer Science & Engineering
City University, Dhaka, Bangladesh.
Anowar Jahid
ID: 1834902059
Batch: 49
th
(eve)
Department of Computer Science & Engineering
City University, Dhaka, Bangladesh.
ACKNOWLEDGEMENT
Project development is not an easy task. It requires cooperation and help of various people. It
always happens that word run out when we are really thankful and sincerely want to inspire our
feeling of gratitude towards the one when helped in the completion of the project.
We are deeply indebted to my supervisor Shahadat Hossain Lecturer and of Department of
Computer Science & Engineering, City University, Dhaka, Bangladesh. Without his help.
guidance, sympathetic co-operation, stimulating suggestions and encouragement, the planning and
development of this project would be very difficult for us.
Our special thanks go to the Head of the Department of CSE, Md. Safaet Hossain, who had given
us the permission and encouraged us to go ahead. We are bound to the Honorable Dean of
Department of Science Faculty, Prof. Dr. Engr. Md. Huamaun Kabir, for his endless support.
I am very grateful to all my faculty teachers who gave me their valuable guides to complete my
graduation. I am also very grateful to all those people who have helped me to complete my project.
Mahmud Islam
ID: 1834902057
Batch: 49
th
(eve)
Department of Computer Science & Engineering
City University, Dhaka, Bangladesh.
Anowar Jahid
ID: 1834902059
Batch: 49
th
(eve)
Department of Computer Science & Engineering
City University, Dhaka, Bangladesh.
Page | III
ABSTRACT
The purpose of the project entitled as “HOSPITAL MANAGEMENT SYSTEM” is to computerize
the Office Management of Hospital to develop software which is user friendly simple, fast, and
cost – effective. It deals with the collection of patient’s information, diagnosis details, etc.
Traditionally, it was done manually. The main function of the system is register and store patient
details and doctor details and retrieve these details as and when required, and also to manipulate
these details meaningfully System input contains patient details, diagnosis details, while system
output is to get these details on to the screen. The Hospital Management System can be entered
using a username and password. It is accessible either by an administrator or receptionist. Only
they can add data into the database. The data can be retrieved easily. The data are well protected
for personal use and makes the data processing very fast.
ABSTRACT
The purpose of the project entitled as “HOSPITAL MANAGEMENT SYSTEM” is to computerize
the Office Management of Hospital to develop software which is user friendly simple, fast, and
cost – effective. It deals with the collection of patient’s information, diagnosis details, etc.
Traditionally, it was done manually. The main function of the system is register and store patient
details and doctor details and retrieve these details as and when required, and also to manipulate
these details meaningfully System input contains patient details, diagnosis details, while system
output is to get these details on to the screen. The Hospital Management System can be entered
using a username and password. It is accessible either by an administrator or receptionist. Only
they can add data into the database. The data can be retrieved easily. The data are well protected
for personal use and makes the data processing very fast.
Page | IV
TABLE OF CONTENTS
CONTENTS PAGE
Declaration I
Acknowledge II
Abstract III
CHAPTER
Chapter- 1: Introduction 1-3
Introduction 1
Motivation 1
Objectives 2
Gantt Chart 2-3
Chapter 2: Background Study 4-5
2.1 Introduction 4
2.3 Expected Outcomes 5
Chapter 3: Specification and Requirements 6-8
3.1 Functional Requirement 6
3.1.1 Features of HMS 6
3.1.2 Software Requirement 6
3.1.3 User of HMS 6
3.1.4 Functionality performed by Customer users 6
3.1.5 Functionality performed 7
3.1.6 Manage patient 7
3.1.7 Manage Department 7
3.1.8 Static Pages and Other Sections 7
3.2 Non-Functional Requirement 7-8
3.2.1 Maintainability 7
3.2.2 Security 7
3.2.3 Performance 8
3.2.4 Reliability 8
Chapter 4: System Analysis and Modeling 9-17
TABLE OF CONTENTS
CONTENTS PAGE
Declaration I
Acknowledge II
Abstract III
CHAPTER
Chapter- 1: Introduction 1-3
Introduction 1
Motivation 1
Objectives 2
Gantt Chart 2-3
Chapter 2: Background Study 4-5
2.1 Introduction 4
2.3 Expected Outcomes 5
Chapter 3: Specification and Requirements 6-8
3.1 Functional Requirement 6
3.1.1 Features of HMS 6
3.1.2 Software Requirement 6
3.1.3 User of HMS 6
3.1.4 Functionality performed by Customer users 6
3.1.5 Functionality performed 7
3.1.6 Manage patient 7
3.1.7 Manage Department 7
3.1.8 Static Pages and Other Sections 7
3.2 Non-Functional Requirement 7-8
3.2.1 Maintainability 7
3.2.2 Security 7
3.2.3 Performance 8
3.2.4 Reliability 8
Chapter 4: System Analysis and Modeling 9-17
Page | V
4.1 Introduction to UML 9
4.2 Use Case Diagram 9-10
4.3 Activity Diagram 11-14
4.4 DFD diagram 15
4.5 ER diagram 16
4.6 Existing System Study 17
4.7 SWOT Analysis 17
Chapter 5: Implementation 18-27
5.1 Home Page of Our Site 18
5.2 Patient Registration page 19
5.3 Login page 19
5.4 Admin dashboard 20
5.5 Admin appointment Check list 20
5.6 Admin Add Doctor 21
5.7 Admin add department 21
5.8 Admin add user 22
5.9 Patient Dashboard 22
5.10 Doctor dashboard 23
5.11 Doctor Appointment list check 23
5.12 Nurse Dashboard 24
5.13 Receptionist Dashboard 24
5.14 Data Model 25
5.15 Full system database 25
5.16 Appointment database 25
5.17 Department section database 26
5.18 User role database 26
5.19 User database 27
5.20 Prescription database 27
Chapter 6: Conclusion 28
Chapter 7: References 29
4.1 Introduction to UML 9
4.2 Use Case Diagram 9-10
4.3 Activity Diagram 11-14
4.4 DFD diagram 15
4.5 ER diagram 16
4.6 Existing System Study 17
4.7 SWOT Analysis 17
Chapter 5: Implementation 18-27
5.1 Home Page of Our Site 18
5.2 Patient Registration page 19
5.3 Login page 19
5.4 Admin dashboard 20
5.5 Admin appointment Check list 20
5.6 Admin Add Doctor 21
5.7 Admin add department 21
5.8 Admin add user 22
5.9 Patient Dashboard 22
5.10 Doctor dashboard 23
5.11 Doctor Appointment list check 23
5.12 Nurse Dashboard 24
5.13 Receptionist Dashboard 24
5.14 Data Model 25
5.15 Full system database 25
5.16 Appointment database 25
5.17 Department section database 26
5.18 User role database 26
5.19 User database 27
5.20 Prescription database 27
Chapter 6: Conclusion 28
Chapter 7: References 29
Page | VI
LIST OF FIGURES
FIGURES PAGE
Figure 4.1 Use Case Diagram 8
Figure 4.2 Activity Diagram 9-13
Figure 4.3 DFD Diagram 14
Figure 4.4 ER Diagram 15
Figure 5.1 Home Page of Our Site 17
Figure 5.2 Patient Registration page 19
Figure 5.3 Login page 19
Figure 5.4 Admin dashboard 20
Figure 5.5 Admin appointment Check list 20
Figure 5.6 Admin Add Doctor 21
Figure 5.7 Admin add department 21
Figure 5.8 Admin add user 22
Figure 5.9 Patient Dashboard 22
Figure 5.10 Doctor dashboard 23
Figure 5.11 Doctor Appointment list check 23
Figure 5.12 Nurse dashboard 24
Figure 5.13 Receptionist dashboard 24
Figure 5.15 Full system Database 25
Figure 5.16 Appointment Database 25
Figure 5.17 Department section database 26
LIST OF FIGURES
FIGURES PAGE
Figure 4.1 Use Case Diagram 8
Figure 4.2 Activity Diagram 9-13
Figure 4.3 DFD Diagram 14
Figure 4.4 ER Diagram 15
Figure 5.1 Home Page of Our Site 17
Figure 5.2 Patient Registration page 19
Figure 5.3 Login page 19
Figure 5.4 Admin dashboard 20
Figure 5.5 Admin appointment Check list 20
Figure 5.6 Admin Add Doctor 21
Figure 5.7 Admin add department 21
Figure 5.8 Admin add user 22
Figure 5.9 Patient Dashboard 22
Figure 5.10 Doctor dashboard 23
Figure 5.11 Doctor Appointment list check 23
Figure 5.12 Nurse dashboard 24
Figure 5.13 Receptionist dashboard 24
Figure 5.15 Full system Database 25
Figure 5.16 Appointment Database 25
Figure 5.17 Department section database 26
Page | VII
Figure 5.18 User role database 26
Figure 5.19 User database 27
Figure 5.20 Prescription database 27
LIST OF TABLES
Figure 1.1 Gantt Chart 3
Figure 5.18 User role database 26
Figure 5.19 User database 27
Figure 5.20 Prescription database 27
LIST OF TABLES
Figure 1.1 Gantt Chart 3
Page | 1
CHAPTER 1
INTRODUCTION
1.1 Introduction
Online hospital management system: A unique cloud-based hospital management system for both
patients and hospital stuffs (Doctors, Management). The primary target of this design is to make
hospital experience better than we currently have. Hospital is a place where no one willingly wants
to visit but there are times when we need to. The old system of hospitals is not very user friendly.
The first big stem is waiting in the queue for long hours. There are lots of other problems that
makes your hospital experience bad. Our main focus is to make peoples life easier in the hour of
need. We are working to design such a system that will reduce a lot of paperwork and save people’s
time. Existing software: You will find hospital management system software in various hospitals
in our country. They have great features to help the hospital but that does not allow the patients to
manage their own data. This is what gave us the initial motivation to build a system where the
system will work for all. To overcome those limitation, we are trying to build a social networking
like site for hospitals that will help everyone working in the hospital and their patients. Let’s
discuss about the system in details and see how it will help us. There are no such things that comes
out without any limitations but we focused to overcome the best we could do. Our main focus was
to determine the features for the patients.
1.2 Motivation
We do not usually visit hospitals unless we need to but this visit does not always give us good
experience. We face various problems there. There is automated hospital management system but
they do not provide any functionality for us. Even the doctors do not have access to their patient’s
data while they are at home. It will be great for the patients to have an application that will keep
them close to their personal data like: prescriptions, test reports and other important materials.
Patients will be able to browse through all the doctors available and ask for appointment for their
desired doctor. A doctor will also experience the similar benefits. This will reduce a lot of paper
works and make things easy for everyone associated with it. I have some personal experience
visiting the hospital and I also have gathered experience from other people by asking them and
observing them for some time. People experience their worst nightmare while they need to visit
the hospital. No body visits the hospital unless it is extremely necessary. People get mad but they
do not have anything to do then. This gave me the perfect motivation to build something for them
and offer them some help at their most needed time. I am confident that this product can and will
help them.
CHAPTER 1
INTRODUCTION
1.1 Introduction
Online hospital management system: A unique cloud-based hospital management system for both
patients and hospital stuffs (Doctors, Management). The primary target of this design is to make
hospital experience better than we currently have. Hospital is a place where no one willingly wants
to visit but there are times when we need to. The old system of hospitals is not very user friendly.
The first big stem is waiting in the queue for long hours. There are lots of other problems that
makes your hospital experience bad. Our main focus is to make peoples life easier in the hour of
need. We are working to design such a system that will reduce a lot of paperwork and save people’s
time. Existing software: You will find hospital management system software in various hospitals
in our country. They have great features to help the hospital but that does not allow the patients to
manage their own data. This is what gave us the initial motivation to build a system where the
system will work for all. To overcome those limitation, we are trying to build a social networking
like site for hospitals that will help everyone working in the hospital and their patients. Let’s
discuss about the system in details and see how it will help us. There are no such things that comes
out without any limitations but we focused to overcome the best we could do. Our main focus was
to determine the features for the patients.
1.2 Motivation
We do not usually visit hospitals unless we need to but this visit does not always give us good
experience. We face various problems there. There is automated hospital management system but
they do not provide any functionality for us. Even the doctors do not have access to their patient’s
data while they are at home. It will be great for the patients to have an application that will keep
them close to their personal data like: prescriptions, test reports and other important materials.
Patients will be able to browse through all the doctors available and ask for appointment for their
desired doctor. A doctor will also experience the similar benefits. This will reduce a lot of paper
works and make things easy for everyone associated with it. I have some personal experience
visiting the hospital and I also have gathered experience from other people by asking them and
observing them for some time. People experience their worst nightmare while they need to visit
the hospital. No body visits the hospital unless it is extremely necessary. People get mad but they
do not have anything to do then. This gave me the perfect motivation to build something for them
and offer them some help at their most needed time. I am confident that this product can and will
help them.
Page | 2
1.3 Objectives
1) Define hospital
2) Recording information about the Patients that come.
3) Generating bills.
4) Recording information related to diagnosis given to patients.
5) Keeping record of the immunization provided to children/patients.
6) Keeping information about various diseases and medicines available to cure them.
These are the various jobs that need to be done in a hospital by the operational staff and Doctors.
All these works are done on papers.
Scope of the Project: -
1) Information about Patients is done by just writing the Patients name, age and gender.
Whenever the Patient comes up his information is stored freshly.
2) Bills are generated by recording price for each facility provided to patient on a separate
sheet and at last they all are summed up.
3) Diagnosis information to patients is generally recorded on the document, which contains
Patient information. It is destroyed after some time period to decrease the paper load in the
office.
4) Immunization records of children are maintained in pre-formatted sheets, which are kept
in a file.
5) Information about various diseases is not kept as any document. Doctors themselves do
this job by remembering various medicines.
All this work is done manually by the receptionist and other operational staff and lot of papers are
needed to be handled and taken care of. Doctors have to remember various medicines available for
diagnosis and sometimes miss better alternatives as they can’t remember them at that time.
1.4 Gantt Chart
Gantt charts are commonly used to track project schedules and are especially effective in project
management. Simply put, they illustrate and allow you to know what needs to be done and when.
Gantt charts are able to show you additional information about the different tasks or categories of
a project, such as how far the work has progressed, how a work group can rely or other work
groups, how important several tasks are and the resources being used in a project.
1.3 Objectives
1) Define hospital
2) Recording information about the Patients that come.
3) Generating bills.
4) Recording information related to diagnosis given to patients.
5) Keeping record of the immunization provided to children/patients.
6) Keeping information about various diseases and medicines available to cure them.
These are the various jobs that need to be done in a hospital by the operational staff and Doctors.
All these works are done on papers.
Scope of the Project: -
1) Information about Patients is done by just writing the Patients name, age and gender.
Whenever the Patient comes up his information is stored freshly.
2) Bills are generated by recording price for each facility provided to patient on a separate
sheet and at last they all are summed up.
3) Diagnosis information to patients is generally recorded on the document, which contains
Patient information. It is destroyed after some time period to decrease the paper load in the
office.
4) Immunization records of children are maintained in pre-formatted sheets, which are kept
in a file.
5) Information about various diseases is not kept as any document. Doctors themselves do
this job by remembering various medicines.
All this work is done manually by the receptionist and other operational staff and lot of papers are
needed to be handled and taken care of. Doctors have to remember various medicines available for
diagnosis and sometimes miss better alternatives as they can’t remember them at that time.
1.4 Gantt Chart
Gantt charts are commonly used to track project schedules and are especially effective in project
management. Simply put, they illustrate and allow you to know what needs to be done and when.
Gantt charts are able to show you additional information about the different tasks or categories of
a project, such as how far the work has progressed, how a work group can rely or other work
groups, how important several tasks are and the resources being used in a project.
Page | 3
ACTIVITIES
WEEKS
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
1.Planning
Discuss project title with
supervisor
Make a project planning
Identify problem Statement
Make abstract of the Project
Identify objectives and Scope
System
2.Analysis
Analysis case Background
Analysis Problem Statement
Analysis literature Review
Submit Proposal to Supervisor
Presentation of the Proposal
Correction of the Proposal
3.Design
Propose Methodology
Design Use Case Diagram
Design Activity Diagram
Design Dataflow Diagram
Submit Report to Supervisor
Report Correction
Seminar Presentation
Submit Final Report
Figure 1.1: Use Case Diagram
ACTIVITIES
WEEKS
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
1.Planning
Discuss project title with
supervisor
Make a project planning
Identify problem Statement
Make abstract of the Project
Identify objectives and Scope
System
2.Analysis
Analysis case Background
Analysis Problem Statement
Analysis literature Review
Submit Proposal to Supervisor
Presentation of the Proposal
Correction of the Proposal
3.Design
Propose Methodology
Design Use Case Diagram
Design Activity Diagram
Design Dataflow Diagram
Submit Report to Supervisor
Report Correction
Seminar Presentation
Submit Final Report
Figure 1.1: Use Case Diagram
Page | 4
CHAPTER 2
BACKGROUND STUDY
2.1 Introduction
Healthcare especially in the developed world is characterized by rapidly increasing use of
information technology in patient care, increasing documentation, coding and billing, and
management. Rise of health information technology worldwide is increasing the efficiency of
health service delivery, reducing medical errors, improving quality of care, and providing better
information for patients and physicians (Pollak and Lorch, 2007). The overall goal of the
information management function is to obtain, manage, and use information to improve health
care and medical services, performance, governance and management and support processes. The
importance of healthcare to individuals and governments and its growing costs to the economy
have contributed to the emergence of healthcare as an important area of research for scholars in
business and other disciplines. In additional, Piontek et al., (2010) asserts that healthcare influences
the quality of human lives and function in the society. Healthcare mistakes have serious
consequences that can affect ability to carry out social and productive endeavors. Recent reports
highlight the gravity of adverse events in hospitals and the dangers such events pose to individuals
and the public. Healthcare information systems have changed the healthcare industry drastically
over the last decade as well as the last few years (Abraham & Junglas, 2011). The forces of
competition and advancements in healthcare technology are pushing hospitals to follow the trend.
Paperless healthcare systems have become inevitable and any healthcare institute that doesn’t
follow this trend will fall behind the rest in the industry. Delone and Mclean (2003) being one of
the most cited models in the fields of information systems seeks to provide a comprehensive
understanding of information systems success by identifying, describing, and explaining the
relationships between six success variables categories: systems quality, information quality, user,
user satisfaction, individual impact, and organizational impact. The same author notes the model
provides a comprehensive frame work for measuring the performance of the information system
and enhances the understanding of information systems success.
Hospital Management System (HMS) is designed for multispecialty hospitals, to cover a wide
range of hospital administration and management processes of patient-centric system. Itis an
integrated end-to-end Hospital Management System that provides relevant information across the
hospital to support effective decision making for patient care (medical records management and
billings), and hospital administration, in a seamless flow. In existence, some researchers have
contributed positively in the improving of health care institutions management systems.
Therefore, we discuss in this section below, some of the related works done in hospital
management system by researchers in the field.
CHAPTER 2
BACKGROUND STUDY
2.1 Introduction
Healthcare especially in the developed world is characterized by rapidly increasing use of
information technology in patient care, increasing documentation, coding and billing, and
management. Rise of health information technology worldwide is increasing the efficiency of
health service delivery, reducing medical errors, improving quality of care, and providing better
information for patients and physicians (Pollak and Lorch, 2007). The overall goal of the
information management function is to obtain, manage, and use information to improve health
care and medical services, performance, governance and management and support processes. The
importance of healthcare to individuals and governments and its growing costs to the economy
have contributed to the emergence of healthcare as an important area of research for scholars in
business and other disciplines. In additional, Piontek et al., (2010) asserts that healthcare influences
the quality of human lives and function in the society. Healthcare mistakes have serious
consequences that can affect ability to carry out social and productive endeavors. Recent reports
highlight the gravity of adverse events in hospitals and the dangers such events pose to individuals
and the public. Healthcare information systems have changed the healthcare industry drastically
over the last decade as well as the last few years (Abraham & Junglas, 2011). The forces of
competition and advancements in healthcare technology are pushing hospitals to follow the trend.
Paperless healthcare systems have become inevitable and any healthcare institute that doesn’t
follow this trend will fall behind the rest in the industry. Delone and Mclean (2003) being one of
the most cited models in the fields of information systems seeks to provide a comprehensive
understanding of information systems success by identifying, describing, and explaining the
relationships between six success variables categories: systems quality, information quality, user,
user satisfaction, individual impact, and organizational impact. The same author notes the model
provides a comprehensive frame work for measuring the performance of the information system
and enhances the understanding of information systems success.
Hospital Management System (HMS) is designed for multispecialty hospitals, to cover a wide
range of hospital administration and management processes of patient-centric system. Itis an
integrated end-to-end Hospital Management System that provides relevant information across the
hospital to support effective decision making for patient care (medical records management and
billings), and hospital administration, in a seamless flow. In existence, some researchers have
contributed positively in the improving of health care institutions management systems.
Therefore, we discuss in this section below, some of the related works done in hospital
management system by researchers in the field.
Page | 5
2.2 Expected Outcomes
HMS (Hospital Management System) otherwise known as HMIS (Hospital Management
Information System) is a medical informatics solution element that mainly focuses on the hospital
administration requirements. The HMS is a web-based or computer application that takes care of
the complete hospital functionalities. The integrated system can be customized and are developed
to control all hospital operations like patient details, appointment booking, billing, drug
management, Electronic Medical Record, administration, Patient medical history, inventory
management, bed management, revenue management and so on. Hospital Management System is
essential and mandatory for healthcare establishments like nursing homes, rehabilitation centers,
clinics, hospitals, health clinics, dispensaries, and more. Some of the top benefits of implementing
an HMS are role-based access control, data accuracy, revenue management, appointment booking,
overall cost reduction, and data security.
2.2 Expected Outcomes
HMS (Hospital Management System) otherwise known as HMIS (Hospital Management
Information System) is a medical informatics solution element that mainly focuses on the hospital
administration requirements. The HMS is a web-based or computer application that takes care of
the complete hospital functionalities. The integrated system can be customized and are developed
to control all hospital operations like patient details, appointment booking, billing, drug
management, Electronic Medical Record, administration, Patient medical history, inventory
management, bed management, revenue management and so on. Hospital Management System is
essential and mandatory for healthcare establishments like nursing homes, rehabilitation centers,
clinics, hospitals, health clinics, dispensaries, and more. Some of the top benefits of implementing
an HMS are role-based access control, data accuracy, revenue management, appointment booking,
overall cost reduction, and data security.
Page | 6
CHAPTER 3
SPECIFICATION AND REQUIREMENT
3.1 Functional Requirement
3.1.1 Features of HMS
➢ Online Appointment Management
➢ Billing Management
➢ Prescription Management
➢ In-Patient Management
➢ Lab Management
3.1.2 Software Requirement
Operating System – Windows 10, 7, Linux (Ubuntu)
Language: PHP (Hypertext Preprocessor)
Framework – Laravel
Database - MySQL
Browser - Any of Mozilla, Opera, Chrome etc.
Web Server - XAMP, WAMP
Software Development Kit – Visual Studio code, PhpStorm
Scripting Language Enable –HTML, CSS, JavaScript, jQuery plugin.
3.1.3 Users of HMS
There are three types of users available in the project
➢ Customer: With limited access. Customers will be able to view home page, blog, contact
us, about us, appointment and also know the status.
➢ Employee: With limited access.
➢ Admin: With full access Admin.
3.1.4 Functionality performed by customer user
➢ Registration for patient
➢ Login for patient
➢ Forgot password for patient
➢ Edit profile for patient
➢ Make a cart to buy multiple products.
➢ View product to choose and check product qualification.
➢ View his/her payment and shopping history.
➢ Customer can also track the order of the products.
CHAPTER 3
SPECIFICATION AND REQUIREMENT
3.1 Functional Requirement
3.1.1 Features of HMS
➢ Online Appointment Management
➢ Billing Management
➢ Prescription Management
➢ In-Patient Management
➢ Lab Management
3.1.2 Software Requirement
Operating System – Windows 10, 7, Linux (Ubuntu)
Language: PHP (Hypertext Preprocessor)
Framework – Laravel
Database - MySQL
Browser - Any of Mozilla, Opera, Chrome etc.
Web Server - XAMP, WAMP
Software Development Kit – Visual Studio code, PhpStorm
Scripting Language Enable –HTML, CSS, JavaScript, jQuery plugin.
3.1.3 Users of HMS
There are three types of users available in the project
➢ Customer: With limited access. Customers will be able to view home page, blog, contact
us, about us, appointment and also know the status.
➢ Employee: With limited access.
➢ Admin: With full access Admin.
3.1.4 Functionality performed by customer user
➢ Registration for patient
➢ Login for patient
➢ Forgot password for patient
➢ Edit profile for patient
➢ Make a cart to buy multiple products.
➢ View product to choose and check product qualification.
➢ View his/her payment and shopping history.
➢ Customer can also track the order of the products.
Page | 7
3.1.5 Functionality performed by Admin users
➢ Login for admin.
➢ Forgot password for admin.
➢ Edit profile for admin.
3.1.6 Manage Patient
➢ Edit the existing patient
➢ View profile of the patient
➢ Listing of all patient
3.1.7 Manage department
➢ Add department
➢ Edit department
➢ Listing of the department
➢ Filter and search department
3.1.8 Static Pages and Other Sections
➢ Home Page with good UI
➢ About Us page describes about the project
3.2 Non-Functional Requirement
3.2.1 Maintainability
Good HMS technologies are easy to maintain. They are usually SaaS-based platforms that can be
upgraded and improved upon remotely without hindering the daily activities of hospitals. Its
maintenance activities can be pre-scheduled in parts considering when the activity is lowest, and
it doesn’t take long to upgrade.
3.2.2 Security
HMS oversees humongous volumes of data generation, information exchange, storage, and
analysis at every level of hospital functioning. As it is based on Cloud and other advanced digital
technologies, it offers strong, multi-layered security to all data exchanges, and thereby protects the
system from misuse or loss of information. The HMS platforms usually comply with the most
stringent data security and privacy policies set in a country. As HMS is hosted on Cloud-based
servers which are located away from the premises, it remains protected from cyberattacks on
hospital systems. Overall HMS promotes transparency, protects the confidentiality, prevents data
theft, and offers a safe and secure ecosystem for hospitals operations to continue.
3.1.5 Functionality performed by Admin users
➢ Login for admin.
➢ Forgot password for admin.
➢ Edit profile for admin.
3.1.6 Manage Patient
➢ Edit the existing patient
➢ View profile of the patient
➢ Listing of all patient
3.1.7 Manage department
➢ Add department
➢ Edit department
➢ Listing of the department
➢ Filter and search department
3.1.8 Static Pages and Other Sections
➢ Home Page with good UI
➢ About Us page describes about the project
3.2 Non-Functional Requirement
3.2.1 Maintainability
Good HMS technologies are easy to maintain. They are usually SaaS-based platforms that can be
upgraded and improved upon remotely without hindering the daily activities of hospitals. Its
maintenance activities can be pre-scheduled in parts considering when the activity is lowest, and
it doesn’t take long to upgrade.
3.2.2 Security
HMS oversees humongous volumes of data generation, information exchange, storage, and
analysis at every level of hospital functioning. As it is based on Cloud and other advanced digital
technologies, it offers strong, multi-layered security to all data exchanges, and thereby protects the
system from misuse or loss of information. The HMS platforms usually comply with the most
stringent data security and privacy policies set in a country. As HMS is hosted on Cloud-based
servers which are located away from the premises, it remains protected from cyberattacks on
hospital systems. Overall HMS promotes transparency, protects the confidentiality, prevents data
theft, and offers a safe and secure ecosystem for hospitals operations to continue.
Page | 8
3.2.3 Performance
By streamlining and integrating multiple processes, HMS infuses much speed, agility, and
efficiency into the system. The platform has specially designed modules for various functions such
as OPD management, IPD management, Cath Lab and diagnostics management, emergency care
response, billing and payments, and operations. It has the ability to offer role-based control to users
to allow them the use of one part of the function or multiple functions and help them monitor and
track every activity necessary for healthcare delivery. Due to such intra-operability and flexible
properties, HMS boosts the performance and capabilities of a healthcare facility in treating
patients.
3.2.4 Reliability
Being software as a service, HMS is highly resilient to any technology disruptions, downtime, or
crashes experienced by other technology systems. It has a certain capacity to work offline. It is
highly secure from a data safety point of view. Furthermore, good HMS has a highly instinctive
and intelligent user interface which makes them convenient to use.
3.2.3 Performance
By streamlining and integrating multiple processes, HMS infuses much speed, agility, and
efficiency into the system. The platform has specially designed modules for various functions such
as OPD management, IPD management, Cath Lab and diagnostics management, emergency care
response, billing and payments, and operations. It has the ability to offer role-based control to users
to allow them the use of one part of the function or multiple functions and help them monitor and
track every activity necessary for healthcare delivery. Due to such intra-operability and flexible
properties, HMS boosts the performance and capabilities of a healthcare facility in treating
patients.
3.2.4 Reliability
Being software as a service, HMS is highly resilient to any technology disruptions, downtime, or
crashes experienced by other technology systems. It has a certain capacity to work offline. It is
highly secure from a data safety point of view. Furthermore, good HMS has a highly instinctive
and intelligent user interface which makes them convenient to use.
Page | 9
CHAPTER 4
SYSTEM ANALYSIS & MODELING
4.1 Introduction to UML
The Unified Modeling Language (UML) is a standard language for specifying, visualizing,
constructing, and documenting the software system and its components. It is a graphical language
which provides a vocabulary and set of semantics and rules. The UML focuses on the conceptual and
physical representation of the system. It captures the decisions and understandings about systems that
must be constructed. It is used to understand, design, configure, maintain, and control information
about the systems.
The UML is a language for:
➢ Visualizing
➢ Specifying
➢ Constructing
➢ Documenting
Visualizing
Through UML we see or visualize an existing system and ultimately, we visualize how the system
is going to be after implementation. Unless we think, we cannot implement. UML helps to
visualize, how the components of the system communicate and interact with each other.
Specifying
Specifying means building, models that are precise, unambiguous and complete UML addresses
the specification of all the important analysis design, implementation decisions that must be made
in developing and deploying a software system.
Constructing
UML models can be directly connected to a variety of programming language through mapping a
model from UML to a programming language like JAVA or C++ or VB. Forward Engineering and
Reverse Engineering is possible through UML.
Documenting
The Deliverables of a project apart from coding are some Artifacts, which are critical in
controlling, measuring and communicating about a system during its developing requirements,
architecture, desire, source code, project plans, tests, prototypes releasers, etc...
4.2 Use Case Diagram
A use case diagram in the Unified Modeling Language (UML) is a type of behavioral diagram
defined by and created from a use-case analysis. Its purpose is to present a graphical overview of
the functionality provided by a system in terms of actors, their goals (represented as use cases),
and any dependencies between those use cases.
Use case diagrams are formally included in two modeling languages defined by the
CHAPTER 4
SYSTEM ANALYSIS & MODELING
4.1 Introduction to UML
The Unified Modeling Language (UML) is a standard language for specifying, visualizing,
constructing, and documenting the software system and its components. It is a graphical language
which provides a vocabulary and set of semantics and rules. The UML focuses on the conceptual and
physical representation of the system. It captures the decisions and understandings about systems that
must be constructed. It is used to understand, design, configure, maintain, and control information
about the systems.
The UML is a language for:
➢ Visualizing
➢ Specifying
➢ Constructing
➢ Documenting
Visualizing
Through UML we see or visualize an existing system and ultimately, we visualize how the system
is going to be after implementation. Unless we think, we cannot implement. UML helps to
visualize, how the components of the system communicate and interact with each other.
Specifying
Specifying means building, models that are precise, unambiguous and complete UML addresses
the specification of all the important analysis design, implementation decisions that must be made
in developing and deploying a software system.
Constructing
UML models can be directly connected to a variety of programming language through mapping a
model from UML to a programming language like JAVA or C++ or VB. Forward Engineering and
Reverse Engineering is possible through UML.
Documenting
The Deliverables of a project apart from coding are some Artifacts, which are critical in
controlling, measuring and communicating about a system during its developing requirements,
architecture, desire, source code, project plans, tests, prototypes releasers, etc...
4.2 Use Case Diagram
A use case diagram in the Unified Modeling Language (UML) is a type of behavioral diagram
defined by and created from a use-case analysis. Its purpose is to present a graphical overview of
the functionality provided by a system in terms of actors, their goals (represented as use cases),
and any dependencies between those use cases.
Use case diagrams are formally included in two modeling languages defined by the
Page | 10
Admin
Doctor
Nurse
Patient
Laboratories
Login
Receptionist
Online Request
Appointment
Cancel
appointmen
t
Sign Up
Doctor List
Assist
Doctor
Test
Guide Patient
Refund
Make
Prescription
Test Report
Include
Include
Include
Extend
Figure 4.1: Use Case Diagram
Admin
Doctor
Nurse
Patient
Laboratories
Login
Receptionist
Online Request
Appointment
Cancel
appointmen
t
Sign Up
Doctor List
Assist
Doctor
Test
Guide Patient
Refund
Make
Prescription
Test Report
Include
Include
Include
Extend
Figure 4.1: Use Case Diagram
Page | 11
4.3 Activity Diagram
The activity diagram used to describe flow of activity through a series of actions. Activity
diagram is an important diagram to describe the system. An activity diagram shows the overall
flow of control.
➢ Admin
Login
Authentication
Check
Invalid
Valid
Logout
Add Doctor Add Patient
Reports
Edit Details
Add Bill
Medicine Bill
Payment Bill
Payment
Patient
Figure 4.2: Activity Diagram
Appointment
Accept
Edit
Edit
4.3 Activity Diagram
The activity diagram used to describe flow of activity through a series of actions. Activity
diagram is an important diagram to describe the system. An activity diagram shows the overall
flow of control.
➢ Admin
Login
Authentication
Check
Invalid
Valid
Logout
Add Doctor Add Patient
Reports
Edit Details
Add Bill
Medicine Bill
Payment Bill
Payment
Patient
Figure 4.2: Activity Diagram
Appointment
Accept
Edit
Edit
Page | 12
➢ Doctor
Login
Authentication
Check
Invalid
Valid
Figure 4.2: Activity Diagram
Logout
View Appointment View Patient List
Add prescription
Edit prescription
➢ Doctor
Login
Authentication
Check
Invalid
Valid
Figure 4.2: Activity Diagram
Logout
View Appointment View Patient List
Add prescription
Edit prescription
Page | 13
➢ Patient
Login
Authentication
Check
Invalid
Valid
Figure 4.2: Activity Diagram
Logout
Add Appointment View Prescription View Doctor list
Cancel Appointment
➢ Patient
Login
Authentication
Check
Invalid
Valid
Figure 4.2: Activity Diagram
Logout
Add Appointment View Prescription View Doctor list
Cancel Appointment
Page | 14
➢ Nurse
Login
Authentication
Check
Invalid
Valid
Figure 4.2: Activity Diagram
Logout
Appointment View Doctor list
➢ Nurse
Login
Authentication
Check
Invalid
Valid
Figure 4.2: Activity Diagram
Logout
Appointment View Doctor list
Page | 15
4.4 DFD diagram
A data flow diagram is a graphical view of how data is processed in a system in terms of input
and output.
The Data flow diagram (DFD) contains some symbol for drawing the data flow diagram
Hospital
Management
System
Hospital Management
Doctor
Management
Patient
Management
System Management
Login Management
Figure 4.3: DFD Diagram
Employee Management
Zero Level DFD – Hospital Management System
4.4 DFD diagram
A data flow diagram is a graphical view of how data is processed in a system in terms of input
and output.
The Data flow diagram (DFD) contains some symbol for drawing the data flow diagram
Hospital
Management
System
Hospital Management
Doctor
Management
Patient
Management
System Management
Login Management
Figure 4.3: DFD Diagram
Employee Management
Zero Level DFD – Hospital Management System
Page | 16
4.5 ER diagram
This ER (Entity Relationship) Diagram represents the model of Hospital Management System
Entity. The entity-re-patronship diagram of Hospital Management System shows all the visual
instrument of database tables and the re-lations between Patient, Nurses, Hospitals, Medicines etc.
It used structure data and to define the relationships between structured data groups of Hospital
Management System functionalities. The main entities of the Hospital Management System are
Hospitals, Patient, Doctors, Nurses, Appointments and Medicines.
Figure 4.4: ER Diagram
Doctor Patient
Medicine
Treats
Id
Name
Address
Fast Name
Last Name
Middle
Name
Phone
Name
Fast Name
Last Name
Middle
Name
Bill
Id
Address
Prescription
Quantity
D_Id
P_Id
Phone
Id
4.5 ER diagram
This ER (Entity Relationship) Diagram represents the model of Hospital Management System
Entity. The entity-re-patronship diagram of Hospital Management System shows all the visual
instrument of database tables and the re-lations between Patient, Nurses, Hospitals, Medicines etc.
It used structure data and to define the relationships between structured data groups of Hospital
Management System functionalities. The main entities of the Hospital Management System are
Hospitals, Patient, Doctors, Nurses, Appointments and Medicines.
Figure 4.4: ER Diagram
Doctor Patient
Medicine
Treats
Id
Name
Address
Fast Name
Last Name
Middle
Name
Phone
Name
Fast Name
Last Name
Middle
Name
Bill
Id
Address
Prescription
Quantity
D_Id
P_Id
Phone
Id
Page | 17
4.6 Existing System Study
In the hospital management there are few systems has already existed which are listed below.
➢ Right now, hospital staff store patient information manually like write on the paper.
➢ Doctor, nurse and others staff check their working schedule by manually.
➢ Invoice and billing are like paper working system.
➢ Patient admit system.
➢ Check operation and checkup.
➢ All record stored physically like in a store house.
4.7 SWOT Analysis
SWOT is an acronym for Strengths, Weaknesses, Opportunities and Threats. Each letter is a vital
component of the tool, which are laid out in a square format with four quadrants, called a SWOT
matrix. The matrix is usually filled in with bulleted lists from left to right, top to bottom
following the order of the word SWOT.
Helpful Harmful
Internal
Strengths
➢ We have online web-based system.
➢ Our system has patient panel for
place online appointment.
➢ This technology help to the patient
so that they can save their time.
➢ User-friendly system.
➢ Doctor can see their appointment
and every hospital staff has their
own panel to their work list.
Weaknesses
➢ It has limited appointment system for
every doctor.
➢ If doctor appointment is full of that day,
then patient has to wait for another day
appointment.
➢ Domain and hosting renew every year.
External
Opportunities
➢ Now it is starting in some of
hospital where they move their all
kinds of job in web-based
management system.
➢ Trying to improve this system to
online payment and also include
accounts section.
Threats
➢ There is no any kind of training for the
patient that how to operate this website.
➢ It will take time to learn how to operate
this.
4.6 Existing System Study
In the hospital management there are few systems has already existed which are listed below.
➢ Right now, hospital staff store patient information manually like write on the paper.
➢ Doctor, nurse and others staff check their working schedule by manually.
➢ Invoice and billing are like paper working system.
➢ Patient admit system.
➢ Check operation and checkup.
➢ All record stored physically like in a store house.
4.7 SWOT Analysis
SWOT is an acronym for Strengths, Weaknesses, Opportunities and Threats. Each letter is a vital
component of the tool, which are laid out in a square format with four quadrants, called a SWOT
matrix. The matrix is usually filled in with bulleted lists from left to right, top to bottom
following the order of the word SWOT.
Helpful Harmful
Internal
Strengths
➢ We have online web-based system.
➢ Our system has patient panel for
place online appointment.
➢ This technology help to the patient
so that they can save their time.
➢ User-friendly system.
➢ Doctor can see their appointment
and every hospital staff has their
own panel to their work list.
Weaknesses
➢ It has limited appointment system for
every doctor.
➢ If doctor appointment is full of that day,
then patient has to wait for another day
appointment.
➢ Domain and hosting renew every year.
External
Opportunities
➢ Now it is starting in some of
hospital where they move their all
kinds of job in web-based
management system.
➢ Trying to improve this system to
online payment and also include
accounts section.
Threats
➢ There is no any kind of training for the
patient that how to operate this website.
➢ It will take time to learn how to operate
this.
Page | 18
CHAPTER 5
IMPLEMENTATION
Implementation of new system can take place to determine the success of the system.
Implementation stages of a system provide user confidence. This procedure has been designed so
that most problems can be managed. The tasks involved in implementation process are given
below.
1. Premises are to be allocated to establishment of new system.
2. Necessary hardware and software components are to be arranged.
3. Production of a complete set of documentation is needed.
4. Every part of development web site is to be tested.
5. Method of changed over is to be planed.
6. Overall system is also to be tested.
5.1 Home Page of Our Site
This is our site home page. In this page patient can see the hospital website overall things, about
us, service, online appointment system and also register theme self.
Fig 5.1: Home page of Hospital management system
CHAPTER 5
IMPLEMENTATION
Implementation of new system can take place to determine the success of the system.
Implementation stages of a system provide user confidence. This procedure has been designed so
that most problems can be managed. The tasks involved in implementation process are given
below.
1. Premises are to be allocated to establishment of new system.
2. Necessary hardware and software components are to be arranged.
3. Production of a complete set of documentation is needed.
4. Every part of development web site is to be tested.
5. Method of changed over is to be planed.
6. Overall system is also to be tested.
5.1 Home Page of Our Site
This is our site home page. In this page patient can see the hospital website overall things, about
us, service, online appointment system and also register theme self.
Fig 5.1: Home page of Hospital management system
Page | 19
5.2 Patient Registration page
This is a registration page, where patient can registration to this hospital website and they can
create online appointment system.
Fig 5.2: Registration page for patient.
5.3 Login page
This is the login page where patient, admin, doctor and others staff can login to their portal.
Fig 5.3: Login page.
5.2 Patient Registration page
This is a registration page, where patient can registration to this hospital website and they can
create online appointment system.
Fig 5.2: Registration page for patient.
5.3 Login page
This is the login page where patient, admin, doctor and others staff can login to their portal.
Fig 5.3: Login page.
Page | 20
5.4 Admin dashboard
This is the admin profile, where admin can see all over things, admin can add doctor, add
department, see appointment and manage it.
Fig 5.4: Admin dashboard
5.5 Admin appointment Check list
Fig 5.5: Admin dashboard pending appointment list
5.4 Admin dashboard
This is the admin profile, where admin can see all over things, admin can add doctor, add
department, see appointment and manage it.
Fig 5.4: Admin dashboard
5.5 Admin appointment Check list
Fig 5.5: Admin dashboard pending appointment list
Page | 21
5.6 Admin Add Doctor
Fig 5.6: Admin add doctor
5.7 Admin add department
Admin can add department.
Fig 5.7: Admin add doctor
5.6 Admin Add Doctor
Fig 5.6: Admin add doctor
5.7 Admin add department
Admin can add department.
Fig 5.7: Admin add doctor
Page | 22
5.8 Admin add user
Admin can add user
Fig 5.8: Admin add user
5.9 Patient Dashboard
This is patient dashboard panel, where patient can see the doctor list and patient
can create appointment.
Fig 5.9: Patient dashboard page
5.8 Admin add user
Admin can add user
Fig 5.8: Admin add user
5.9 Patient Dashboard
This is patient dashboard panel, where patient can see the doctor list and patient
can create appointment.
Fig 5.9: Patient dashboard page
Page | 23
5.10 Doctor dashboard
In this part doctor can see their appointment in list.
Fig 5.10: Doctor dashboard page
5.11 Doctor Appointment list check
Fig 5.11: Doctor appointment list check.
5.10 Doctor dashboard
In this part doctor can see their appointment in list.
Fig 5.10: Doctor dashboard page
5.11 Doctor Appointment list check
Fig 5.11: Doctor appointment list check.
Page | 24
5.12 Nurse dashboard
In this part nurse can also check their panel for working schedule.
Fig 5.12: Nurse dashboard page
5.13 Receptionist dashboard
This is the receptionist page where they can check the appointment list.
Fig 5.13: Receptionist dashboard page
5.12 Nurse dashboard
In this part nurse can also check their panel for working schedule.
Fig 5.12: Nurse dashboard page
5.13 Receptionist dashboard
This is the receptionist page where they can check the appointment list.
Fig 5.13: Receptionist dashboard page
Page | 25
5.14 Data Model
Data models are visual representations of the data elements of an enterprise and the connections
between them. By helping to define and structure data in terms of relevant business processes, the
models support the development of effective information systems. They enable business and
technological resources to collaboratively decide how data will be stored, accessed, shared,
updated and leveraged across an organization. In this section shows the table that contains in online
tutor finder database. These tables will show all attribute with data type, primary key and foreign
key.
Fig 5.14: Full system database
Fig 5.15: Appointment database
5.14 Data Model
Data models are visual representations of the data elements of an enterprise and the connections
between them. By helping to define and structure data in terms of relevant business processes, the
models support the development of effective information systems. They enable business and
technological resources to collaboratively decide how data will be stored, accessed, shared,
updated and leveraged across an organization. In this section shows the table that contains in online
tutor finder database. These tables will show all attribute with data type, primary key and foreign
key.
Fig 5.14: Full system database
Fig 5.15: Appointment database
Page | 26
Fig 5.16: Department section database
Fig 5.17: User role database
Fig 5.16: Department section database
Fig 5.17: User role database
Page | 27
Fig 5.18: User database
Fig 5.19: Prescription database
Fig 5.18: User database
Fig 5.19: Prescription database
Page | 28
CHAPTER 6
CONCLUSION
Conclusion
This was an excellent project to work on and I have learned a lot of things to complete this project.
A lot of new idea and several problems that may happen to a system like this is quite clear for me
now. Our creativity makes us different from every other species on this planet. We build tools and
machines to make our lives easy and more comfortable. This has begun at a very early age and
since then we have never stopped to build or design new things. Due to this creativity our planet
has become very something totally different than our ancestors experienced. AI – artificial
intelligence is an old concept but our current approach has taken it to a different height. We have
been able to build things that has changed the entire thinking process of human civilization.
Medical technology has also improved along with other sectors of science. Once people used to
die of different diseases but we have overcome those by our advancement in various sectors.
Automation in medical sector is still quite new but the question is for how long this will remain
new. Researches are advancing to perform diagnosis and prescribe medicine for people without a
doctor. Of course, there are doctors for supervisions
CHAPTER 6
CONCLUSION
Conclusion
This was an excellent project to work on and I have learned a lot of things to complete this project.
A lot of new idea and several problems that may happen to a system like this is quite clear for me
now. Our creativity makes us different from every other species on this planet. We build tools and
machines to make our lives easy and more comfortable. This has begun at a very early age and
since then we have never stopped to build or design new things. Due to this creativity our planet
has become very something totally different than our ancestors experienced. AI – artificial
intelligence is an old concept but our current approach has taken it to a different height. We have
been able to build things that has changed the entire thinking process of human civilization.
Medical technology has also improved along with other sectors of science. Once people used to
die of different diseases but we have overcome those by our advancement in various sectors.
Automation in medical sector is still quite new but the question is for how long this will remain
new. Researches are advancing to perform diagnosis and prescribe medicine for people without a
doctor. Of course, there are doctors for supervisions
Page | 29
CHAPTER 7
REFERENCES
REFERENCES
1. A. Lorch, J. and E. Pollak, &., 2007. Computerized patient record in dialysis practice.
[online] springer.
2. Abraham, C. and Junglas, I., 2011. From cacophony to harmony: A case study about the
IS implementation process as an opportunity for organizational transformation at Sentara
Healthcare.
3. Delone, W. and McLean, E., 2003. The DeLone and McLean Model of Information
Systems
4. John Svirbely, M. and John Svirbely, M., 2022. Can Algorithms Help with Medical Patient
Education?
5. GitHub. 2022. GitHub - kishan0725/Hospital-Management-System: Hospital
Management System using php and Mysql.
CHAPTER 7
REFERENCES
REFERENCES
1. A. Lorch, J. and E. Pollak, &., 2007. Computerized patient record in dialysis practice.
[online] springer.
2. Abraham, C. and Junglas, I., 2011. From cacophony to harmony: A case study about the
IS implementation process as an opportunity for organizational transformation at Sentara
Healthcare.
3. Delone, W. and McLean, E., 2003. The DeLone and McLean Model of Information
Systems
4. John Svirbely, M. and John Svirbely, M., 2022. Can Algorithms Help with Medical Patient
Education?
5. GitHub. 2022. GitHub - kishan0725/Hospital-Management-System: Hospital
Management System using php and Mysql.
Tags
Download
Download Slideshow Get the original presentation fileQuick Actions
Statistics
- Views 1,566
- Slides 37
- Age 645 days
Related Slideshows
36
Clinical approach Dyspnoea A simple and practical approach.pptx
ShajahanPS
24 views
238
Cancer Awareness therapy for public by Dr Kanhu Charan Patro
kanhucpatro
24 views
41
Prof Satyadas Memorial oration Kozhikode.pptx
ShajahanPS
19 views
26
Viral Conjunctivitis and it;s managment.pptx
ZaidAzhar
34 views
30
Essential Thrombocythemia 15 Years of Experience at the Hematology Department, Algies, Algeria.pdf
sbelakehal
29 views
10
Hypertension sign symptoms cmdt style with regime
androiddabest
30 views