Hospital Management System
AUTHENTICATION
By
Shreeya Shrestha
Symbol: 24458/076
This Report Presented in Partial Fulfillment of the Requirements for the Degree
of Bachelor of Science in Computer Science and Information Technology
Supervised by:
Suman Makai Shrestha
Assistant Professor
Department of CSIT
Tribhuvan University
Tribhuvan University
Department of Computer Science & Information Technology
Faculty of Computer Science and Information Technology
Submitted by: Submitted
to:
Name: Shreeya Shrestha Suman Makai
Shrestha
Symbol: 24458/076 Department of CSIT
Banepa Nist College
Name: Nirjala Dahal
Symbol: 24447/076
Name: Sabina Dahal
Symbol: 24453/076 Course code:
CSC315
Abstract
Hospital Management System provides the benefits of streamlined operations, enhanced
Administration & control, superior patient care, strict cost control and improved
profitability. HMS is powerful, flexible, and easy to use and is designed and developed to
deliver real conceivable benefits to hospitals. More importantly it is backed by reliable
and dependable support.
The project ‘Hospital Management System’ is based on the database, object oriented and
networking techniques. As there are many areas where we keep the records in database
for which we are using MY SQL software which is one of the best and the easiest
software to keep our information. This project uses JAVA as the front-end software
which is an Object Oriented Programming and has connectivity with MY SQL.
Hospital Management System is custom built to meet the specific requirement of
the mid and large size hospitals across the globe. All the required modules and features
have been particularly built to just fit in to your requirement. This package has been
widely accepted by the clients in India and overseas. Not stopping only to this but they
are highly satisfied and appreciating. Entire application is web based and built on 3 tier
architecture using the latest technologies. The sound database of the application makes it
more users friendly and expandable. The package is highly customizable and can be
modified as per the needs and requirements of our clients. Prolonged study of the
functionalities of the hospital and its specific requirement has given it a wonderful shape
both technically and usability wise. It covers all the required modules right from Patient
Registration, Medicine details, Doctor, Wards, , Admin, Store, Patient appointment, bill
payment, record modification, discharge details etc.
Acknowledgement
I would like thanks to all those who are involved in this endeavor for their kind
cooperation for its successful completion. At the outset, I wish to express our sincere
gratitude to all those people who helped me to complete this project in an efficient
manner.
I offer my special thanks to my project supervisor Suman Makai Shrestha, Assistant
Professor, Department of Computer Science and Information Technology, Tribhuvan
University, Banepa, Kavre without whose help and support throughout this project would
not have been this success. His guidance helped me in all the time of my project and
writing of this project report.
We are really thankful to all of my friends who always advised and motivated me
throughout the course.
Contents
Introduction..............................................................................................................................1
1.1 Problem Statement............................................................................................................1
1.2 Objective...........................................................................................................................1
1.3 Scope................................................................................................................................1
2) Project Management............................................................................................................2
2.1 Project planning and scheduling.......................................................................................2
2.1.1 Methodology..............................................................................................................2
2.1.2 Project Management Life Cycle................................................................................2
2.1.3 Project Plan:...............................................................................................................3
2.1.4 Schedule Representation...........................................................................................3
2.2 Risk Management.............................................................................................................4
3) System Analysis....................................................................................................................4
3.1 Background Study............................................................................................................4
3.2 Software system attributes................................................................................................4
3.2.1 Reliability:.................................................................................................................4
3.2.2 Availability:...............................................................................................................4
3.2.3 Security:.....................................................................................................................4
3.3 Scope of working:.............................................................................................................4
3.4 Feasibility study................................................................................................................5
3.4.1 Technical Feasibility:................................................................................................5
3.4.2 Operational Feasibility:.............................................................................................5
3.4.3 Economic Feasibility:................................................................................................5
3.4.4 Management Feasibility:...........................................................................................5
3.4.5 Social Feasibility:......................................................................................................5
4) System Design.......................................................................................................................5
4.1 Database Design...............................................................................................................5
4.2 E-R Diagram of Hospital Management System...............................................................6
4.3 Database schema of Hospital Management System.........................................................6
4.4 Data Flow Diagram of Hospital Management System...............................................7-10
4.5 User Interface.................................................................................................................10
4.5.1 Home Page...............................................................................................................10
4.5.2 Admin login page....................................................................................................10
4.5.3 Admin user details page..........................................................................................11
4.5.4 Appointment History page......................................................................................11
4.5.5 User (Patient) login page.........................................................................................12
4.5.6 User account create page.........................................................................................12
4.5.7 User Details page.....................................................................................................13
4.5.8 Doctor Login page...................................................................................................13
5) System Implementation.....................................................................................................14
5.1 Implementation...............................................................................................................14
5.2 Implementation Environment.........................................................................................14
5.3 Functional Requirement.................................................................................................14
5.3.1 Administrator Interface...........................................................................................14
5.3.2 User Interface..........................................................................................................14
6) System Testing....................................................................................................................15
6.1 Integration Testing..........................................................................................................15
6.2 Unit Testing....................................................................................................................15
6.3 System Testing...............................................................................................................15
6.4 Acceptance Testing........................................................................................................15
6.5 Recovery Testing............................................................................................................15
6.6 Functional Testing..........................................................................................................15
6.7 Hardware/Software Testing............................................................................................15
6.8 Security Testing..............................................................................................................15
6.9 Advantages.....................................................................................................................15
7) Conclusion...........................................................................................................................16
7.1 Conclusions....................................................................................................................16
7.2 Limitations of the system...............................................................................................16
7.3 Future plan......................................................................................................................16
References................................................................................................................................16
Introduction
Human Body is a very complex and sophisticated structure and comprises of millions of
functions. As science and technology progressed, medicine became an integral part of the
research. Gradually, medical science became an entirely new branch of science. As of today, the
Health Sector comprises of Medical institutions i.e. Hospitals, research and development
institutions and medical colleges. Thus the Health sector aims at providing the best medical
facilities to the common people.
1.1 Problem Statement
Since Hospital is associated with the lives of common people and their day-to-day routines so I
decided to work on this project.
The manual handling of the record is time consuming and highly prone to error. The
purpose of this project is to automate or make online, the process of day-to-day activities like
Room activities, Admission of New Patient, Discharge of Patient, Assign a Doctor, and finally
compute the bill etc. I have tried my best to make the complicated process Hospital Management
System as simple as possible using Structured & Modular technique & Menu oriented interface. I
have tried to design the software in such a way that user may not have any difficulty in using this
package & further expansion is possible without much effort. Even though I cannot claim that this
work to be entirely exhaustive, the main purpose of my exercise is perform each Hospital’s
activity in computerized way rather than manually which is time consuming.
I am confident that this software package can be readily used by non-programming
personal avoiding human handled chance of error.
1.2 Objective
Hospital are the essential part of our lives, providing best medical facilities to people suffering
from various ailments, which may be due to change in climatic conditions, increased work-load,
emotional trauma stress etc. It is necessary for the hospitals to keep track of its day-to-day
activities & records of its patients, doctors, nurses, ward boys and other staff personals that keep
the hospital running smoothly & successfully.
But keeping track of all the activities and their records on paper is very cumbersome and error
prone. It also is very inefficient and a time-consuming process Observing the continuous increase
in population and number of people visiting the hospital. Recording and maintaining all these
records is highly unreliable, inefficient and error-prone. It is also not economically & technically
feasible to maintain these records on paper. Thus keeping the working of the manual system as
the basis of our project. We have developed an automated version of the manual system, named
as “Administration support system for medical institutions”.
The main aim of our project is to provide a paper-less hospital up to 90%. It also aims at
providing low-cost reliable automation of the existing systems. The system also provides
excellent security of data at every level of user-system interaction and also provides robust &
reliable storage and backup facilities.
1.3 Scope
The proposed software product is the Hospital Management system. The system will be used in any
hospital, clinic, dispensary or pathology labs. Clinic, dispensary or pathology to get the information
from the patients and then storing that data for future usages. The intention of the system is to reduce
over-time pay and increase the number of patients that can be treated accurately. Requirement
statements in these documents are both functional and non- functional.
2) Project Management
2.1 Project planning and scheduling
Project planning is part of project management, which relates to the use of schedules such as
Gantt charts to plan and subsequently report progress within the project environment.
Initially, the project scope is defined and the appropriate methods for completing the project
are determined. Following this step, the durations for the various tasks necessary to complete
the work are listed and grouped into a work breakdown structure. The logical dependencies
between tasks are defined using an activity network diagram that enables identification of the
critical path.
2.1.1 Methodology
We have used Iterative and Incremental Development model (IID) for our project
development. This development approach is also referred to as Iterative Waterfall
Development approach. Iterative and Incremental Development is a software development
process developed in response to the more traditional waterfall model. This model is designed
to take care of such big project. The large and complicate project chiefly demand better
development and testing procedure. The waterfall model is well known for its repeated testing
process. Hence I choose the waterfall model for developing my software.
Figure : Waterfall model
Some advantages of waterfall model:
o Simple and easy to understand and use.
o Easy to manage due to the rigidity of the model.
o Phases are processed and completed one at a time
o Works well for smaller projects where requirements are very well understood.
2.1.2 Project Management Life Cycle
The Project Management Life Cycle has four phases. Each project life cycle phase is
described along with the tasks need to complete it.
The four phases are Initiation, planning, execution and closure.
Figure: Iterative and Incremental Life
2.1.3 Project Plan:
Once we examine that the project is feasible, I undertake project planning. The table below
describes how we planned my project.
Table 2.1 Project Plan
1 Task Name Duration Start Finish
2 Planning 31 days 12/05/23 12/06/23
3 Design 28 days 01/07/23 29/07/23
4 Coding 29 days 14/03/23 12/04/23
5 Delivery 8 days 13/04/23 20/04/23
2.1.4 Schedule Representation
Scheduling the project tasks is an important project planning activity. It involves deciding
which tasks would be taken up when. In order to schedule the project activities, a software
project manager needs to do the following this rules.
Figure : Gantt chart
2.2 Risk Management
Software Risk Management is a proactive approach for minimizing the uncertainty and
potential loss associated with a project. Some categories of risk include product size, business
impact, customer related, process, technology, development environment, staffing (size and
experience), schedule, and cost. Risk Management is a practice with processes, methods, and
tools for managing risks in a project.
Risk identification is a systematic attempt to specify threats to the project plan. By identifying
known and predictable risks, we can take a first step toward avoiding them when possible and
controlling them when necessary. To perform the risk identification, we categorized the risk
into different categories as:
1.Project Risk
2.Technical Risk
3.Business Risk
4.Known Risk
5.Predictable Risk
6.Unpredictable Risk
3) System Analysis
3.1 Background Study
System Analysis is a separation of a substance into parts for study and their implementation
and detailed examination. Before designing any system it is important that the nature of the
business and the way it currently operates are clearly understood. The detailed examination
provides the specific data required during designing in order to ensure that all the client's
requirements are fulfilled. The investigation or the study conducted during the analysis phase
is largely based on the feasibility study. Rather it would not be wrong to say that the analysis
and feasibility phases overlap. High-level analysis begins during the feasibility study. Though
analysis is represented as one phase of the system development life cycle (SDLC), this is not
true. Analysis begins with system initialization and continues until its maintenance. Even
after successful implementation of the system, analysis may play its role for periodic
maintenance and up gradation of the system. One of the main causes of project failures is
inadequate understanding, and one of the main causes of inadequate understanding of the
requirements is the poor planning of system analysis.
3.2 Software system attributes
3.2.1 Reliability: This application is a reliable product that produces fast & verified output of
all its process.
3.2.2 Availability: This application will be available to use and help them to carry their
operations conveniently.
3.2.3 Security: This application will be designed in a maintainable manner. It will be easy to
incorporate new requirements in the individual modules.
3.3 Scope of working:
The proposed software product is the Hospital Management system (HMS). The system will
be used in any hospital, clinic, dispensary or pathology labs. Clinic, dispensary or pathology
to get the information from the patients and then storing that data for future usages. The
current system in use is a paper based system. It is too slow and cannot provide updated lists
of patients within reasonable timeframe. The intention of the system is to reduce over-time
pay and increase the number of patients that can be treated accurately. Requirement
statements in these documents are both functional and non-functional.
3.4 Feasibility study
3.4.1 Technical Feasibility: This is concerned with specifying equipment and software that
will successfully satisfy the user requirement; the technical needs of the system may vary
considerably, but might include:
The facility to produce outputs in a given time:
Response time under conditions.
Ability to process a certain volume of transaction at a particular seep.
Facility to communicate data to distant location.
3.4.2 Operational Feasibility: It is mainly related to human organization and political
aspects. The points to be considered are:
What changes will be brought with the system?
What organizational structures are distributed?
What new skills will be required? Do the existing staff members have these skills? If not, can
then the trained due course of time
3.4.3 Economic Feasibility: Economic analysis is the most frequently used technique for
evaluating the effectiveness of a proposed system. More frequently known as cost/benefit
system and compare them with costs. If benefits outweigh costs, a decision is taken to design
and implement the system.
3.4.4 Management Feasibility: It is a determination of whether a proposed project will be
acceptable to management. If does not accept a project of gives a negligible support to it; the
analyst will tend to view the project as a no feasible one.
3.4.5 Social Feasibility: Social feasibility is a determination of whether the project will be
acceptable to the people or not. This determination typically examines the probability of the
project accepted by the group directly affected by the proposed system change.
4) System Design
4.1 Database Design
Database design is the process of producing a detailed data model of database. This data
model contains all the need logical and physical design choices and physical storage
parameters needed to generate a design in a data definition language, which can then be used
to create a database. A fully attributed data model contains detailed attributes for each entity.
The term database design can be used to describe many different part of the design of an
overall database system. Principally, and most correctly, it can be thought of as the logical
design of the base data structure used to store the data. In the relational model these are the
tables and views. In an object database the entities and relationships map directly to object
classes and named relationships. However, the term database design could also be used to
apply to the overall process of designing, not just the base data structure, but also the forms
and queries used as part of the overall database application within the database management
system.
4.2 E-R Diagram of Hospital Management System
An entity-relationship diagram (ERD) is an abstract and conceptual representation of data.
Entity relationship modeling is a database modeling method, used to produce a type of
conceptual schema or semantic data model of a system, often a relational database, and its
requirements in a top-down fashion.
hospital patients
Patient Admit
information
Room
Hospital Doctor Doctor
record
Patient On Line Hospital
Appointment
Fig : E-R Diagram of Online Marketplace
4.3 Database schema of Hospital Management System
A database schema is the skeleton structure that represents the logical view of the entire
database. It defines how the data is organized and how the relations among them are
associated. It formulates all the constraints that are to be applied on the data.
A database schema can be divided broadly into two categories −
Physical Database Schema: This schema pertains to the actual storage of data and its form
of storage like files, indices, etc. It defines how the data will be stored in a secondary storage.
Logical Database Schema: This schema defines all the logical constraints that need to be
applied on the data stored. It defines tables, views, and integrity constraints.
List of table:
1.admin
2.Users
3.Patients
4.Physician
5.Services
6.Transactions
7.user_details
8.Room
9.Discounts
10.Appointment
11.Doctors
12.Doctor specialization.
Fig : Database schema of Online Marketplace
4.4 Data Flow Diagram of Hospital Management System
The context diagram is the most abstract data flow representation of a system. It represents
the entire system as a single bubble and. The various external entities with which the system
interacts and the data flows occurring between the system and the external entities are also
represented. The name context diagram is well justified because it represents the context in
which the system is to exist i.e. the external entities (users) that would interact with the
system and specific data items they would be receiving from the system.
Figure : Data flow diagram of online marketplace
DFD: Level 0
Entity Relationship Diagram
4.5 User Interface
4.5.1 Home Page
Actor: Any users
Figure: Home page
Flow:
1. Any user can browsers this page.
4.5.2 Admin login page
Actor: Admin users
Output: Banepa Medical Center
Figure : Admin Login page
Flow:
Only Admin user can browsers this page.
Admin user can search all patient appointment and all users’ activities.
4.5.3 Admin user details page
Actor: Admin users
Output: Admin details page
Figure : Admin details page
Flow:
Admin user can browsers this page.
Admin user can view all module here
4.5.4 Appointment History page
Actor: Admin users
Output: Appointment History.
Figure: Verified user profile page
Flow:
Admin user can browsers this page.
Admin user can view all appointment history.
4.5.5 User (Patient) login page
Actor: User.
Input: User email and Password Output: User profile page.
Flow:
(1) User Logs in with user email and password.
Alternate Flow:
If the user email is wrong then it is asked to login again.
If the password is wrong then the user is asked to enter again.
4.5.6 User account create page
Actor: User.
Input: User name, email, password and confirm password.
Output: Create a new user and show user profile page.
Flow:
(1)Password must be more than 8 cheater.
(2) Password and confirm password must be same
Alternate Flow:
If the mandatory fields are not fill up then alert is shown.
If password less than 8 cheater or password and confirm password not match alert is shown.
4.5.7 User Details page
Actor: User.
Flow:
(1) User must be fill up all input field.
Alternate Flow:
(1) If the mandatory fields are not fill up then alert is shown.
4.5.8 Doctor Login page
Actor: User.
Flow:
(1) User Logs in with user email and password.
5) System Implementation
5.1 Implementation
Implementation is the process of having system personal check out and provides new
equipment’s into use, train the user to install a new application and construct any files of data
needed to use it. There are three types of implementation. Implementation of computer
system to replace a manual system. To problem encountered are covering files, training user,
creating accurate files and verifying print outs for integrity. Implementation of a new
computer system to replace an existing one. This is usually difficult conversion. If not
properly planned, there can be many problems. So large computer system many take as long
as a year to convert. Implementation of a modified application to replace the existing one
using the same computer. This type of conversing is relatively easy to handle, usually there
are no major change in the file. Our project is yet to be implemented.
5.2 Implementation Environment
The implementation view of software requirement presents the real world manifestation of
processing functions and information structures. This computerized system is specified in a
manner that dictates accommodation of certain implementation details.
The implementation environment of the developed system facilitates multiple users to use this
system simultaneously. The user interfaces are designed keeping in mind that the users of this
system are familiar to using GUI-based systems. Thus, we restricted ourselves to developing
a GUI-based system so that it becomes easier for the end user to get acquainted to the
developed system.
5.3 Functional Requirement
This system interface is divided into two section
Administrator interface.
Users interface.
5.3.1 Administrator Interface
Administrator can delete any post.
Administrator can verified user account.
5.3.2 User Interface
User can browse all ads without any account.
For post an ad needs to create an account
User can update/edit their own account.
Log in and Log out system.
To create a new account user must be needs to verify his email with verification code.
If any user forget his/her password he/she can recovery his account with verify his email and
create a new password.
6) System Testing
6.1 Integration Testing
Integration testing done before, during and after integration of a new module into the main
software package. This involves testing of each individual code module. One piece of
software can contain several modules which are often created by several different
programmers. It is crucial to test each modules effect on the entire program model. After
integration testing the project works successfully.
6.2 Unit Testing
Unit testing performed on each module or block of code during development. Unit testing is
normally done by the programmer who writes the code.
6.3 System Testing
System testing done by a professional testing agent on the completed software product before
it is introduced to the market.
6.4 Acceptance Testing
Acceptance testing is a beta testing of the product done by the actual end user.
6.5 Recovery Testing
Recovery testing is done to demonstrate a software salutation is reliable, trustworthy and can
successfully recoup form possible crashes.
6.6 Functional Testing
Functional Testing also known as functional completeness testing. Functional Testing
involves trying to think of any possible missing functions. Testers might make a list of
additional functionalities that a product could to improve it during functional testing.
6.7 Hardware/Software Testing
IBM refers to Hardware/Software testing as “HW/SW Testing”. This is when the tester
focuses his/her attention on the interactions between the hardware and software during system
testing.
6.8 Security Testing
Security Testing is a variant of Software Testing which ensures, that system and applications in
an organization, are free from any loopholes that may cause a big loss. Security testing of any
system is about finding all possible loopholes and weaknesses of the system which might result
into a loss of information at the hands of the employees or outsiders of the Organization.
6.9 Advantages
The software helps to handle the entire administration of hospitals and healthcare facilities.
Typically, such a software includes various modules that help doctors manage their assignments
and schedules, carry out patient registration, maintain store inventory records, keep track of
medicine, administration, maintain blood bank (with available blood type) details, individual
record of patients with their test reports, nursing, financial information, including final billing &
payments, insurance details and much more. After the customized software is implemented and
integrated into the system, patient care and hospital administration becomes an easy job.
7) Conclusion
7.1 Conclusions
This project has been a rewarding experience in more than one way. The entire project work
has enlightened us in the following areas.
We have gained an insight into the working of the HOSPITAL. This represents a typical real
world situation.
Our understanding of database design has been strengthened this is because in order to
generate the final reports of database designing has to be properly followed.
Scheduling a project and adhering to that schedule creates a strong sense of time
management.
Sense of teamwork has developed and confidence of handling real life project has increased
to a great extent.
Initially, there were problem with the validation but with discussions, we were to implement
validations.
7.2 Limitations of the system
Online payment is not available at this version.
Data delete & edit system is not available for all section.
User account not verified by Mobile SMS not available in this system.
Loss of data due to mismanagement.
7.3 Future plan
o Diagnostics billing system.
References
1) Deepak Thomas ͞”Beginning PHP 4 Databases”, Wrox Press Ltd. Paperback-17, October,
2002.70-130 pp.
2) Matt Doyle, “Beginning PHP 5.3, 2ndedition”, October 2009. 150-270 pp.
3) Luke Welling, Laura Thomson. Sams ͞PHP and MySQL Web Development, 2nd edition,
Paperback- 20 February, 2003. 105-209 pp.
4) W. Jason Gilmore “Beginning PHP 5 and MySQL 5 from Novice to Professional
SECOND
EDITION”, Jul 9, 2008.100-150 pp.
5) Abraham Silberschatz, Henry F. Korth and S. Sudarshan “Sixth Edition Database System
Conceptsreleased”, January 28, 2010. 206-253 pp.
6) Server-Side Scriptinghttp://php.net/manual/en/index.php ,
7) HTML &CSS https://www.w3schools.com/,
8) Bootstraphttp://getbootstrap.com/,
9) https://stackoverflow.com/ ,
