Roll No: 49 December 30, 1899

Table of Contents
Table of Contents..................................................................................................................1-2
Chapter 1: Introduction..........................................................................................................3
1.1 Background...................................................................................................................3-4
1.2 Objective...........................................................................................................................5
1.3 Purpose, scope and Applicability.....................................................................................6
1.3.1 Purpose.......................................................................................................................6
1.3.2 Scope..........................................................................................................................6
1.3.3 Applicability..............................................................................................................6
1.4 Existing System of Hospital Management
System……………………………………...7
1.5 Propsed System of Hospital Management
System……………………………………….7

Chapter 2: Survey of Technologies.........................................................................................8

Chapter 3: Requirement Analysis..........................................................................................9
3.1 Problem Definition.........................................................................................................10
3.2 Requirement Specification.............................................................................................10
3.3 Planning and Scheduling................................................................................................10
3.3.1 Gantt chart:..............................................................................................................10
3.4 Software and Hardware Requirements...........................................................................11
3.5 Conceptual model...........................................................................................................13
3.5.1 Event Table..............................................................................................................14
3.5.2 Use Case Diagram...................................................................................................15
3.5.3 Sequence Diagram...................................................................................................16
3.5.4 Class Diagram..........................................................................................................17
3.5.5 State Diagram.....................................................................................................18-19
Chapter 4: System Design.....................................................................................................20
4.1 Basic Module.............................................................................................................20
4.2 Data Base Design...........................................................................................................20
4.2.1 Schema Design........................................................................................................20
4.2.2 Data Relationship Design........................................................................................21
4.3 User Interface Design................................................................................................22-26

Page | 1
Roll No: 49 December 30, 1899

4.4 Implementation Methodology........................................................................................27

4.5 Test Case Design………………………………………………………………………28
4.6 Reports………………………………………………………………………………..29
4.7Conclusion…………………………………………………………………………….30
4.8 Future Scope/Enhancement of the Project…………………………………………...31
4.9 References……………………………………………………………………………32

Page | 2
Roll No: 49 December 30, 1899

Chapter 1: Introduction

The project Hospital Management system includes registration of patients, storing

their details into the system, and also computerized billing in the pharmacy, and labs. The
software has the facility to give a unique id for every patient and stores the details of every
patient and the staff automatically. It includes a search facility to know the current status of
each room. User can search availability of a doctor and the details of a patient using the id.
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 interface is very user-friendly. The data are well
protected for personal use and makes the data processing very fast. Hospital Management
System is powerful, flexible, and easy to use and is designed and developed to deliver real
conceivable benefits to hospitals.

Hospital Management System is a software product suite designed to improve the

quality and management of hospital management in the areas of clinical process analysis and
activity-based costing. Hospital Management System enables you to develop your
organization and improve its effectiveness and quality of work. Managing the key processes
efficiently is critical to the success of the hospital helps you manage your processes

1.1Background
Hospital Management System is a system enabling hospitals to manage information
and data related to all aspects of healthcare – processes, providers, patients, and more, which
in turn ensures that processes are completed swiftly and effectively. When one thinks of the
various aspects and departments of a hospital, it becomes apparent that an HMS is critical.
The hospital database management system was introduced in 1960, and has greatly evolved
since then – with the ability to integrate with the existing facilities, technologies, software,
and systems of a hospital. Today, patients can begin the process of healthcare in the palm of
their hand – the mobile devices and apps – make this possible. This process then moves to the
healthcare providers and hospitals.

Page | 3
Roll No: 49 December 30, 1899

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 interface is very user-friendly. The data are
well protected for personal use and makes the data processing very fast. A person summarizes
all the data of the courier in a register, this work require a high-level of attention since it has
to be taken care that no wring entry goes into the register. This repetitive work may lead to
errors in the entry thus resulting in the wrong entry of courier packed data. Since the data is
maintained in the registers, the modification of data cannot done easily. The previous
information has to be erased and overwritten or a new page has to be allocated so that both
the old and new information can be written on the same page. The summarizing of the data
i.e. preparation of an up to data report is very complex, it require a lot of hard work and
searching through the different registered as to condense the data for presentation.

Page | 4
Roll No: 49 December 30, 1899

1.2 Objective
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.

At its core, HMS aims to simplify the workflow for clinicians, reduce
administrative costs, diminish errors, and provide a better patient experience. However,
it encompasses a wide variety of functions, as the system manages every department or
branch of the hospital.It accumulates doctors, patients, laboratory results, medical
supplies, appointments, bills and insurance, and reports. The main objective of the
Project on Hospital Management System is to manage the details of Hospital, Doctors,
Patient, Employee, Test. It manages all the information about Hospital, Medicine, Test,
Hospital. The project is totally built at administrative end and thus only the administrator
is guaranteed the access. The purpose of the project is to build an application program to
reduce the manual work for managing the Hospital, Doctors, Medicine, Patient. It tracks
all the details about the Patient, Employee, Test.

Page | 5
Roll No: 49 December 30, 1899

1.3 Purpose, scope and Applicability

1.3.1 Purpose
Through this package we provide a fully customized web application. This system is
an automated system so that the functional working of it is effective and time saving. In this
modern era time is the most precious thing, so in context of time the new system will be
effective to do a group of task in easy and secure manner.

1.3.2 Scope
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.3.3 Applicability

 In computer system the person has to fill the various forms & number of copies
of the forms can be easily generated at a time.
 In computer system, it is not necessary to create the manifest but we can directly
print it, which saves our time.
 To assist the staff in capturing the effort spent on their respective working areas.
 To utilize resources in an efficient manner by increasing their productivity
through automation.
 The system generates types of information that can be used for various
purposes.

Page | 6
Roll No: 49 December 30, 1899

1.4.Existing System of Hospital Management System:

In the existing system the exams are done only manually but in proposed system we
have to computerize the exams using this application.
 Lack of security of data.
 More man power.
 Time consuming.
 Consumes large volume of pare work.
 Needs manual calculations.
 No direct role for the higher officials

1.5.Proposed System of Hospital Management System:

The aim of proposed system is to develop a system of improved facilities. The
proposed system can overcome all the limitations of the existing system. The system
provides proper security and reduces the manual work.
 Security of data.
 Ensure data accuracy’s.
 Proper control of the higher officials.
 Minimize manual data entry.
 Minimum time needed for the various processing.
 Greater efficiency.
 Better service.
 User friendliness and interactive.
 Minimum time required.

Page | 7
Roll No: 49 December 30, 1899

Chapter 2: Survey of Technologies

Front End- Python
Python is one of the most exciting development technologies on offer today. Here was
a powerful platform with lots of built-in functionality, astonishing performance levels, and
one of the best IDEs (Integrated Development Environments) around: Visual Studio.
ASP.NET showed the way for the faster, easier and more disciplined development of
dynamic web sites, and the results were impressive.

ASP.NET is a server-side Web application framework designed for Web development

to produce dynamic Web pages. It was developed by Microsoft to allow programmers to
build dynamic web sites, web applications and web services. It was first released in January
2002 with version 1.0 of the .NET Framework, and is the successor to Microsoft's Active
Server Pages (ASP) technology. ASP.NET is built on the Common Language Runtime
(CLR), allowing programmers to write ASP.NET code using any supported .NET language.

Back End – Python(Django)

Django has everything. Developers never feel lost while building an application with Django.
It has ORM, authentication, html templating, template engine, URL routing, view layers,
model layers, and a lot of major components. Combined with Python, Django becomes
unstoppable in developing dynamic web applications. This also leads to faster MVP
development, providing more time to market the products.

Extensible library
Python has a robust and powerful library for building web applications. ANy custom
software development company would suggest using Python because it offers modules that
reduce the time to write code from scratch. There are plugins and libraries for string
operations, operating system interface, and everything else. There is a library of modules for
almost every functionality.

Page | 8
Roll No: 49 December 30, 1899

Chapter 3: Requirement Analysis

3.1 Problem Definition
Lack of immediate retrievals: - The information is very difficult to retrieve and to find
particular information like- E.g. - To find out about the patient’s history, the user has to go
through various registers. This results in in convenienceand wastage of time.
Lack of immediate information storage: - The information generated by various
transactions takes time and efforts to be stored at right place.

3.2 Requirement Specification

On the basis of system study performed in a service are about all the functions that
deal with online service system following requirements are specified.

1. Functional requirements:-
 At the Login module email and password facilitate and credentials should be
checked properly at the time of login for customer or the agent or the admin.

 System also do auto distribution and allocation of goods and products according
location and schedule date and time.

 At result module display the result of pickup and drop challan for all vehicle.

 This web portal access through internet or intranet.

2. Non-function Requirements:-
 The system should be reliable and robust.

 The system should be User friendly.

 The system should be completely Consistent and Secure.

3. Interface requirements:-
Interface should be easy to follow, Interface shouldn’t have very much graphics,
Interface should have hidden buttons, and Interface should produce relevant error
message. In a complete way, we’re expected to build a web based application which
accommodates all functionality of an organization that deal with online auction.

Page | 9
Roll No: 49 December 30, 1899

Page | 10
Roll No: 49 December 30, 1899

3.3 Planning and Scheduling

3.3.1 Gantt chart:

Page | 11
Roll No: 49 December 30, 1899

3.4 Software and Hardware Requirements

Software Requirements:
 Front End: Python
 Development Environment: Python IDLE
 Back End: Python/Django
 Operating System: Window 10

Hardware requirements:
 Operating System: Windows 7 or Higher
 Hard disk: Minimum 500GB
 RAM: Minimum 4GB

Page | 12
Roll No: 49 December 30, 1899

3.5 Conceptual model

3.5.1 Event Table

Event Trigger Source Use Case Response Destination

A patient Register
Appointment
request for an Patient Appointme Confirmation Patient
details
appointment nt

Doctor wants to Diagnosis/ Record

record patient treatment Doctor Diagnosis/t - -
visit results information reatment

Time to Generate
Appointment
generate - <System> appointme Doctor
list
appointment list nt list

Time to
Generate
generate call - Call list Admin
call list
list

Admin wants to
Diagnosis/
calculate fee for Calculate
treatment Admin Receipt Patient
diagnosis/treat fee
information
ment

Patient wants to Diagnosis/ Fill

pay fee through treatment Admin insurance - -
insurance information claim form

Admin wants to
Maintain
update patient Patient
Admin patient - -
employer details
details
details

Page | 13
Roll No: 49 December 30, 1899

3.6.2 Use Case Diagram

Page | 14
Roll No: 49 December 30, 1899

3.6.3 Sequence Diagram

Page | 15
Roll No: 49 December 30, 1899

3.6.4 Class Diagram

Page | 16
Roll No: 49 December 30, 1899

3.6.5 State Diagram

1.Patient

Page | 17
Roll No: 49 December 30, 1899

2.Doctor

Page | 18
Roll No: 49 December 30, 1899

Chapter 4: System Design

4.1.1 Basic Module

Admin

 Signup their account. Then Login (No approval Required).

 Can register/view/approve/reject/delete doctor (approve those doctor who applied for
job in their hospital).
 Can admit/view/approve/reject/discharge patient (discharge patient when treatment is
done).
 Can Generate/Download Invoice pdf (Generate Invoice according to medicine cost,
room charge, doctor charge and other charge).
 Can view/book/approve Appointment (approve those appointments which is requested
by patient).

Doctor

 Apply for job in hospital. Then Login (Approval required by hospital admin, Then
only doctor can login).
 Can only view their patient details (symptoms, name, mobile ) assigned to that doctor
by admin.
 Can view their discharged(by admin) patient list.
 Can view their Appointments, booked by admin.
 Can delete their Appointment, when doctor attended their appointment.

Patient

 Create account for admit in hospital. Then Login (Approval required by hospital
admin, Then only patient can login).
 Can view assigned doctor's details like ( specialization, mobile, address).
 Can view their booked appointment status (pending/confirmed by admin).
 Can book appointments.(approval required by admin)
 Can view/download Invoice pdf (Only when that patient is discharged by admin).

Page | 19
Roll No: 49 December 30, 1899

4.2 Data Base Design

4.2.1 Schema Design

E-R Diagram

Page | 20
Roll No: 49 December 30, 1899

4.2.2 Data Relationship Design

Admin Table
Column Name Data types Constraint
Username Varchar(25) Primary key, Not Null
Name Varchar(25) Not null
Password Varchar(25) Not null
Mobile Number int Not null
Email Varchar(25) unique

Doctor Table
Column Name Data types Constraint
Username int Primary key, Not null
id int Foreign key
Mobile Number int Not null
message Varchar(25) Not null

Patient Table:
Column Name Data types Constraint
Username int Primary Key, not null
Name Varchar(25) Not null
Email Varchar(25) Unique
Password Varchar(25) Not null

Feedback Details :-
Column Name Data Types Constrain
Name Varchar(25) Primary Key,Not null
Email Varchar(25) Not null
Message Varchar(max) Null Null

Page | 21
Roll No: 49 December 30, 1899

4.3 User Interface Design and Coding

Screenshot
1.Home Page

Implementation
Admin

Page | 22
Roll No: 49 December 30, 1899

Doctor and Patient

Page | 23
Roll No: 49 December 30, 1899

2.Admin Dashboard

Implementation

Admin Registration

Page | 24
Roll No: 49 December 30, 1899

Page | 25
Roll No: 49 December 30, 1899

Invoice

Implementation

Page | 26
Roll No: 49 December 30, 1899

Page | 27
Roll No: 49 December 30, 1899

Implementation Methodology:
Model View Controller or MVC as it is popularly called, is a software design pattern for
developing web applications. A Model View Controller pattern is made up of the
following three parts:
 Model - The lowest level of the pattern which is responsible for maintaining data.
 View - This is responsible for displaying all or a portion of the data to the user.
 Controller - Software Code that controls the interactions between the Model
and View.
MVC is popular as it isolates the application logic from the user interface layer and
supports separation of concerns. Here the Controller receives all requests for the
application and then works with the Model to prepare any data needed by the View. The
View then uses the data prepared by the Controller to generate a final presentable response.
The MVC abstraction can be graphically represented as follows.

MVC (Model View Controller Flow) Diagram

Page | 28
Roll No: 49 December 30, 1899

4.5 Test Case Design

Test cases Input specified Expected result Actual result

Username=””
Username empty Username empty
Password=””
User login
Username=”neeraj” Verify and redirect Verify and redirect
Password=”abc03” to home page to home page
Please enter email Please enter email
Please enter valid Please enter valid
Profile=”image” image extension and image extension
file size and file size
Verify File Content-
Profile type check is
Picture enabled, so that if Valid extension
file extension is and file size then it
Profile=”image.png”
changed then will upload profile
uploader should picture
detect the File type
and take action
Specify your mobile Specify your
Mobile number=9890673267
number mobile number
Mobile
Enter correct mobile Enter correct
number Mobile number=9890673267
number mobile number
Mobile number=9890673267 Mobile enter valid Mobile enter valid
Please enter future Please enter future
Date=23/09/1998
date date
Date= Please enter date Please enter date
Date
Automatically
Automatically enters
Date=20/10/2019 enters and accepts
and accepts date.
date.

Page | 29
Roll No: 49 December 30, 1899

Reports

Invoice After discharging patient accordingly charges automated generated bill

Page | 30
Roll No: 49 December 30, 1899

Conclusion of the Project Hospital Management System:

Our project is only a humble venture to satisfy the needs to manage their project
work. Several user friendly coding have also adopted. This package shall prove to be a
powerful package in satisfying all the requirements of the school. The objective of
software planning is to provide a frame work that enables the manger to make reasonable
estimates made within a limited time frame at the beginning of the software project and
should be updated regularly as the project progresses.

At the end it is concluded that we have made effort on following points…

 A description of the background and context of the project and its relation to
work already done in the area.
 Made statement of the aims and objectives of the project.
 The description of Purpose, Scope, and applicability.
 We define the problem on which we are working in the project.
 We describe the requirement Specifications of the system and the actions that
can be done on these things.
 We understand the problem domain and produce a model of the system, which
describes operations that can be performed on the system.
 We included features and operations in detail, including screen layouts.
 We designed user interface and security issues related to system.
 Finally the system is implemented and tested according to test cases.

Page | 31
Roll No: 49 December 30, 1899

Future Scope/Enhancement of the Project:

In a nutshell, it can be summarized that the future scope of the project circles
around maintaining information regarding:

 We can add printer in future.

 We can give more advance software for Hospital Management System including
more facilities
 We will host the platform on online servers to make it accessible worldwide
 Integrate multiple load balancers to distribute the loads of the system
 Create the master and slave database structure to reduce the overload of the
database queries
 Implement the backup mechanism for taking backup of codebase and database on
regular basis on different servers

The above mentioned points are the enhancements which can be done to increase the
applicability and usage of this project. Here we can maintain the records of Hospital
and Doctors. Also, as it can be seen that now-a-days the players are versatile,
i.e. so there is a scope for introducing a method to maintain the Hospital Management
System. Enhancements can be done to maintain all the Hospital, Doctors, Patient,
Employee, Test.

We have left all the options open so that if there is any other future requirement
in the system by the user for the enhancement of the system then it is possible to
implement them.In the last we would like to thanks all the persons involved in the
development of the system directly or indirectly. We hope that the project will serve its
purpose for which it is develop there by underlining success of process.

Page | 32
Roll No: 49 December 30, 1899

References and Bibliography:

 Google for problem solving
 http://pythonproject.com
 http://stackoverflow.com
 http://www.tutorial.com/
 Python and Software Design Concepts by Apress
 https://www.tutorialspoint.com/python/
 https://Pythontutorial.com/Django
 https://github.com
 https://mscw.ac.in/

Page | 33