A Project Report on

“CIMS Hospital Management System”

Submitted in partial fulfillment of the requirement
For MCA - Semester V
Prepared for Subject: MCA 507 - Mini Project II

Prepared By
Kirit G. Thakor : 219SMCA10919

From

MCA Programme,
Narsinhbhai Institute of Computer Studies & Management
Kadi
 PROJECT CERTIFICATE

This is to certify that the project report compiled by Thakor kiritkumar Ganeshbhai

of MCA Semester- V, NICSM, KADI has completed his/her project titled as “CIMS

Hospital Management System” satisfactorily.

We appreciate the enthusiasm & dedication towards work submitted.

Internal Project Guide Head of the Department

Ms.Roshani B Sirja Rakesh K. Patel

1.1 Project Profile:

Project Title CIMS Hospital Management System

Project Duration 4 Months

Front End PHP

Back End My Sql

Internal Project Ms. Roshani Sirja

Guide

Submitted To Narsinbhai Institute of Computer Studies and Management

Team Size 1

Team Members 1.Kirit Thakor

Names
 INDEX Page No
1.0 INTRODUCTION 5
1.0
1
1.1 Project Definition 6
1.2 Existing System 7
1.3 Need for New System 7
2.0 REQUIREMENT ANALYSYS 8
2.1 Proposed System and Targeted Users 9
2.2 System Requirement Specification 10
2.3 Proposed Time-line Chart 11
2.4 Data Dictionary 12
3.0 REQUIREMENT MODELING 24
3 . 1 System Diagrams 25
3.1.1 Class Diagram 26
3.1.2 Use Case Diagrams 27
3.1.3 Activity Diagrams 28
3.1.4 Sequence Diagrams 29
4.0 SYSTEM DEVELOPMENT 30
4.1 Input Forms Screenshots 31
4.2 Output Form Screenshots 35
4.3 Report Screenshots 38
5.0 TESTING 43
6.0 CONCLUSION 46
7.0 REFERENCES 47
1.0 INTRODUCTION
1.1 Project Definition:
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 inaccessible
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 designed for multispecialty hospitals, to cover a wide
range ofhospital administration and management processes. It is an integrated end-to-end
Hospital Management System that provides relevant information across the hospital to support
effective decision making for patient care, hospital administration and critical financial
accounting, in a seamless flow.
1.2 Existing System:
➢ Hospitals currently use a manual system for the management and maintenance of
critical information.
➢ The current system requires numerous paper forms, with data stores spread throughout
the hospital management infrastructure Often information is incomplete or does not
follow management standards.
➢ Forms are often lost in transit between departments requiring a comprehensive auditing
process to ensure that no vital information is lost.
➢ Multiple copies of the same information exist in the hospital and may lead to
inconsistencies in data in various data stores.
➢ The current manual system has a lot of paper work.
➢ To maintain the records of sale and service manually, is a Time-consuming task with the
increase.
➢ In database, it will become a massive task to maintain the database.

1.3 Need for New System:

➢ A Hospital Management System (HMS) is typically a computer-based or a web-based
software system that helps manage the various complicated processes and workflows
that are inherent to the regular working of a hospital.
➢ It provides interfaces for the various stakeholders of a hospital (or any medical facility,
for that matter) to capture, access, manage and report information about every single
aspect of the hospital’s functioning.
➢ Our present modern information system makes use of computers for the execution,
each of them connected through an optimized network. Healthcare is the most critical
aspect of our society, and many health care providers face challenges to offer practical
and active services to patients.
➢ If you are ready to implement or go with the hospital management system, make sure
you follow these things before making it useful in your hospitals or labs.
✓ Processing Speed & Results
✓ Cost Effective
✓ Reduction in Errors
✓ Data Security & Retrieving Ability
✓ Improved Patient Care
✓ Quality & Compliance
2.0 REQUIREMENT ANALYSYS
2.1 Proposed System and Targeted Users:
➢ The Hospital Management System is designed for any hospital to replace their existing
manual paper based system.
➢ The new system is to control the information of patients. Room availability, staff and
operating room schedules and patient invoices.
➢ These services are to be provided in inefficient, cost effective manner, with the goal of
reducing the time and resources currently required for such tasks.
➢ The complete set of rules & procedure related to hospital’s day to day activities and
generating report is called “HOSPITAL MANAGEMENT SYSTEM”.
➢ It is a computerized management system.
➢ This system also keeps the records of hardware assets besides software of this
organization.
➢ The proposed system will keep a track of doctors, patient & receptionist.
➢ This project has GUI based software that will help in storing, updating and retrieving the
information thought various user-friendly menu-driven modules.
➢ The Target market includes patients and families, communities, doctors, medical
personnel, hospital staff, and society Hospital marketing has three functions first, from
the hospital's point of view, through analysis of the target market, hospitals can
understand the future needs of consumers and establish good.
2.2 System Requirement Specification:
❖ HARDWARE REQUIREMENTS:
➢ The most common set of requirements defined by any operating system or software
application is the physical computer resources, also known as hardware. A hardware
requirements list is often accompanied by a hardware compatibility list (HCL),
especially in case of operating systems. An HCL lists tested, compatibility and
sometimes incompatible hardware devices for a particular operating system or
application. The following sub-sections discuss the various aspects of hardware
requirements.

• HARDWARE REQUIREMENTS FOR PRESENT PROJECT:

➢ Server side:
✓ Processer: Intel dual Core, i3
✓ Ram: 1 GB
✓ Hard disk: 1 TB (Minimum 80 GB)
➢ Client side:
✓ Processor:- Intel dual Core, i3
✓ RAM:-4 GB
✓ Hard disk:- 1 TB (Minimum 80 GB)

❖ SOFTWARE REQUIREMENTS:
➢ Software Requirements deal with defining software resource requirements and pre-
requisites that need to be installed on a computer to provide optimal functioning of
an application. These requirements or pre-requisites are generally not included in
the software installation package and need to be installed separately before
the software is installed.

• SOFTWARE REQUIREMENTS FOR PRESENT PROJECT:

➢ Server side:
✓ Operating system: - window XP or other OS
✓ Web server:-Apache Tomcat 7.0.34 Or Above
✓ Data base server: - MySQL
✓ Front End: - PHP
✓ Back End:-MySQL
➢ Client side:
✓ Operating system: - window XP or other OS
✓ Browser:-Internet Explorer 6.0 or Above
2.3 Proposed Time-line Chart:
2.4 Data Dictionary:

1. Table Name: Registration

FIELD NAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION

User_Id Int 5 Primary Key Registration Id

User_Name Varchar 50 Not Null Name

City Varchar 16 Not Null City

Address Varchar 30 Not Null Address

Email Varchar 25 Not Null Email

Password Varchar 40 Not Null Password

Contact_No Number 10 Not Null Contact Number

2. Table Name: Doctor

FIELD NAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION

Doctor_Id Varchar 10 Primary key Doctor id

Doctor name Varchar 30 Not Null Doctor Name

Department Varchar 20 Not Null Department

3. Table Name: Designation

FIELD NAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION

Designation_Id Bigint 10 Primary key AutoNumber

DesignationName Varchar 50 Not Null Define Employee

4. Table Name: Patient
FIELD NAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION

Patient_Id Bigint 20 Primary Key AutonNumber

PatientFirstName Varchar 50 Not Null Identifies Patient

PatientLastName Varchar 50 Not Null Identifies Patient

DateOfBirth DateTime 10 Not Null DOB

Address Varchar 150 Not Null Address

ContectNo.1 Number 10 Not Null Contact Number

Age Int 10 Not Null Age

Gender Varchar 10 Not Null Gender

Doctor_Id Varchar 20 Foreign Key Doctor

Room_Id Varchar 20 Foreign Key Room

5. Table Name: Patient Complain

FIELD NAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION

PatientComplain_id Bigint 20 Primary Key PatientComplainId

Patient_id Bigint 20 Foreign Key PatientId

Complain_id Bigint 20 Foreign Key ComplainId

Description Varchar 200 Not Null Des.

6. Table Name: Complain

FIELD NAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION

Complain_Id Bigint 50 Primary Key ComplainId

Complain_Name Varchar 50 Not Null Complain Name

7. Table Name: Appointment
FIELD NAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION

Appointment_Id Bigint 20 Primary Key AutoNumber

Employee_Id Bigint 20 Foreign Key EmployeeId

Patient_id Bigint 20 Foreign Key Patientid

Patient_Name Varchar 50 Not Null Name

AppointmentDateandTim DateTime 15 Not Null DateandTime

e

DateOfAppointmentTake DateTime 15 Not Null DateOfAppointmentT

n aken

AppointmentTakenById Bigint 25 Not Null AppointmentTakenByI

d
8. Table Name: Employee
FIELD NAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION

Employee_Id Bigint 20 Primary Key Emp. id

Designation_Id Bigint 30 Foreign Key Designation Table

EmployeeFirstName Varchar 30 Not Null First Name

EmployeeLastName Varchar 30 Not Null Last Name

Qualification Bigint 25 Not Null Qualification Of

Employee

Address Varchar 150 Not Null Address

ContactNo.1 Number 10 Not Null Contact Number

Username Varchar 30 Not Null Username of Employee

Password Varchar 30 Not Null Password of Employee

Active Bigint 20 Not Null It identify Employee is

active

Admin Varchar 20 Not Null Admin

9. Table Name: Medicine
FIELD NAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION

Medicine_Id Bigint 20 Primary Key AutoNumber

Medicine_Name Varchar 50 Not Null MedicineName

MedicineType_Id Varchar 20 Foreign Key MedicineType

Company_Id Varchar 20 Foreign Key CompanyId

MedicineDose Varchar 20 Not Null Identifies The Dose

10. Table Name: MedicineType

FIELD NAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION

MedicineType_Id Bigint 20 Primary Key Med. Type

MedicineType_Name Varchar 20 Not Null Med. Name

11. Table Name: Company

FIELD NAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION

Company_Id Bigint 20 Primary Key CompanyId

Company_Name Varchar 50 Not Null Com. Name

12. Table Name: Room
FIELD NAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION

Room_No Varchar 10 Primary key AutoNumber

Room_Type Varchar 20 Not Null RoomType

Status Varchar 20 Not Null Status

13. Table Name: Bill

FIELD NAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION

Bill_No Number 20 Primary key AutoNumber

Patient_Id Number 20 Foreign key Pat.Id

Patient_Type Varchar 25 Allow Null Pat.Type

Doctor_Charge Int 150 Not Null Doc.Charge

Madichine_Charge Int 150 Not Null Mad.Charge

Room_Charge Int 100 Not Null Room_charge

Operation_Charge Int 100 Allow Null Op.Charge

No_Of_Day Int 100 Allow Null Day

Nursing_Charge Int 100 Allow Null Nursing Charge

Lab_Charge Int 100 Allow Null Lab Charge

14. Table Name: Lab
FIELD NAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION

Lab_No Varchar 5 Primary Key Lab number

Patient_Id Varchar 5 Not Null Patient

Weight Int 100 Not Null Weight

Doctor_Id Varchar 5 Foreign Key Doctor

DateTime Date/Time 20 Not Null Date & Time

Category Varchar 15 Not Null Category

Patient_Type Varchar 15 Not Null Patient type

Amount Bigint 100 Not Null Amount

15. Table Name: Case

FIELD NAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION

Case_Id Bigint 20 Primary Key AutoNumber

Employee_Id Bigint 20 Foreign Key Emp. Study The Case

Patient_Id Bigint 20 Foreign Key Define The Patient

Case

Appointment_Id Bigint 20 Foreign Key Patient Appointment

DateAndTime DateTime 15 Not Null Define DateTime

Previous Surgery Varchar 150 Not Null History About Patient

Payment Decimal 10,0 Not Null Doctor Fees

16. Table Name: Staff
FIELD NAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION

Emp_Id Bigint 20 Primary key Auto number

EmpFirstName Varchar 30 Not Null It define EmployeeFirstName

EmpLastName Varchar 30 Not Null It define EmployeeLastName

Qualifications Varchar 80 Not Null It define Qualifications of

Employee

Address Varchar 150 Not Null Address of Employee

Contact_no1 Number 10 Not Null Contact no of home

Username Varchar 30 Not Null Username of Employee

Password Varchar 30 Not Null Password of Employee

Active Bigint 20 Not Null It identify Employee is active

17. Table Name: Operation
FIELD NAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION

Operation_Id Bigint 20 Primary Key AutoNumber

Employee_Id Bigint 20 Foreign Key Employee Id

Patient_Id Bigint 20 Foreign Key Patient Case

OperationDate DateTime 15 Not Null Oper. Date

OperationStartTime DateTime 10 Not Null Patient Oper. Start

Time

OperationEndTime DateTime 10 Not Null Patient Oper. End

Time

OperationTypeId Bigint 25 Foreign Key OperationType

18. Table Name: OperationType

FIELD NAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION

OperationTypeId Bigint 20 Primary Key AutoNumber

OperationTypeName Varchar 40 Not Null Oper. Name

3.0 REQUIREMENT MODELING
3.1 System Diagrams
3.1.1 Class Diagram:
3.1.2 Use Case Diagrams:
3.1.3 Activity Diagrams:
3.1.4 Sequence Diagrams:
4.0 SYSTEM DEVELOPMENT
4.1 Input Forms Screenshots:

1. Login:

2. Designation:
3. Patient:

4. Patient Complain:

5. Appointment:
6. Employee:

7. Medicine:

8. MedicineType:
9. Case:

10. Operation:
4.2 Output Form Screenshots:

1. Designation:

2. Patient:

3. Patient Complain:
4. Appointment:

5. Employee:

6. Medicine:
7. MedicineType:

8. Case:

9. Operation:
4.3 Report Screenshots:

1.
2.
3.
4.

5.
6.
5.0 TESTING
 Testing Phase

One of the purpose of the testing is to validate and verify the system. Verification
means checking the system to ensure that it is doing what the function is supposed
to do and validate means checking to ensure that system is doing what the user
wants it is do.

1. Commination between the user and the designer.

2. The Programmer’s ability to generate a code that reflects exactly the system
specification.
3. The time frame for the design.
 1. Unit testing:
This is the smallest testable unit of a computer system and is normally tested using
the white box testing. The author of the programmer usually carries out unit tests.

2. Integration testing:
In integration testing, the different units of the system are integrated together to
from the complete system and this type of testing checks the system as whole to ensure that it
is doing what is supposed to do.

3. System testing:
A part of testing the system to validate the functionality of software against the
requirements, it is also necessary to test the non-functional aspect of the system.

System testing consists of the following steps:

1. Program testing
2. String testing
3. System testing
4. System documentation

4. Field testing:
This is a special type of testing that may be very important in some project. Here the
system is tested in actual in the actual operation surrounding.
6.0 CONCLUSION:
This project has been a rewarding experience in more than one way. The entire project
work has enlightened us in the following areas.
a) We have gained an insight into the working of the HOSPITAL. This represents a typical
real-world situation.
b) 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.
c) Scheduling a project and adhering to that schedule creates a strong sense of time
management.
d) Sense of teamwork has developed and confidence of handling real life project has
increased to great extent.
e) Initially, there were problem with the validation but with discussions, we were to
implement validations.
7.0 REFERENCES:

[1] Deepak Thomas “Beginning PHP 4 Databases”, Word Press Ltd.

[2]Matt Doyle, “Beginning PHP 5.3, 2nd edition”.
[3] Luke Welling, Laura Thomson. Sam’s-PHP and MySQL Web Development.
[4]W. Jason Gilmore “Beginning PHP 5 and MySQL 5 from Novice to Professional SECOND
EDITION”.
[5]Abraham Silberschatz, Henry F. North and S. Sudarshan “Sixth Edition Database System
Concepts released”.
[6] Server-Side Scriptinghttp://php.net/manual/en/index.php, Last accessed.
[7] HTML &CSS https://www.w3schools.com/, Last accessed.
[8] Bootstrap phttp://getbootstrap.com/, last accessed.
[9]https://stackoverflow.com/, last accessed.