Hsms

A
Project Report
On
Hospital Management System
Submitted By
Group No: 24
Patel Preksha Manishkumar (En. No:-21082221073)
Vaghela Khushiba Dilipsinh (En. No:-21082221096)
B. Sc. (CA & IT) – V

U15A5PRI: INDUSTRIAL PROJECT – I
Guided By
Prof. Nishil N. Prajapati
Submitted to
Department of Computer Science,
Ganpat University (GUNI),
Ganpat Vidyanagar – 384012
Academic Year 2023-2024
Date: 16 /12 / 2022
CERTIFICATE
TO WHOM SO EVER IT MAY CONCERN
This is to certify that the following students of B.Sc. (CA & IT) Semester-V have completed
their project work titled “Hospital Management System” satisfactorily and fulfill the
requirement of B.Sc. (CA & IT) Semester-V, Department of Computer Science, Ganpat
University in the academic year 2023-2024.
Sr. No. Student Name Enrollment No.
1. Patel Preksha Manishkumar 21082221073
2. Vaghela Khushiba Dilipsinh 21082221096
Internal Guide Project Coordinator Program Coordinator Principal
Prof. Nishil prajapati Prof. Asha Patel Dr. Ketan Patel Dr. Nirbhay Chaubey
ACKNOWLEDGMENT
We Here by acknowledgment appreciation and deep gratitude to the persons without whose
support this project would never been seen the light of the day.We express my sincere thanks to
Prof. Asha Patel, Project Coordinator for extending her help.We have immense pleasure in
expressing thanks and deep sense of gratitude to my guide Prof. Nishil Patel and the entire
Faculty in DCS for his valuable suggestion and guidance throughout this project.Finally, at the
outset we would like to thank all those who have directly or indirectly helped us accomplish our
project successfully.
TEAM MEMBER :
Patel Preksha M. (21082221073)
Vaghela Khushiba D.
(21082221096)
PREFACE
This Hospital Management System project is a computerized hospital front desk

management that produces user-friendly, quick, and cost-effective software. It handles and
secures patient information, diagnosis data, and so on. This was done by hand and its’ principal
job is to register and maintain patient and doctor information and to access and update the
information when needed.
Patient information and diagnosis are entered into the system, then the output is used to
display these details on the screen. A username and password are required to access the Hospital
Management System. It can be accessed by a receptionist or an administrator. They are the only
ones who have access to the database. The information is easily accessible. For personal usage,
the data is well-protected, and the data processing is quick.
CONTENTS
Sr. No. Particulars Page No.
1. Project Profile 1
2. Existing System 2
3. Need for New System 3
4. Functional Specification 4
4.1 User of The System
4.2 Module of The System
5. System Requirement 6
5.1 Minimum Software Requirements
5.2 Minimum Hardware Requirements
6. System Flow Diagram 8
7. E-R Diagram 9
8. Data Flow Diagram 10
9. Data Dictionary 14
10. Input Design & Output Design 20
11. Testing 40
12. Future Enhancement 44
13. Bibliography 45
Department of Computer Science Group No-24
1.PROJECT PROFILE
Project Profile: Hospital Management System (PulsePower Suite):
Objective: The purpose of the Hospital Management System is a user-

friendly software that automates front desk tasks in a hospital.
It securely manages patient and doctor information, providing
quick access and updates. Restricted to authorized personnel,
the system ensures data protection and efficient processing,
contributing to cost-effectiveness.
Platform of Application: Web Site
Front End Tool: PHP , CSS , HTML , Java Script , Bootstrap
Back End Tool: MY SQL, PHP
Other Tool: Visual Studio Code
Project Duration: 90 Days
Internal Project Guide: Prof.Nishil Prajapati
Submitted By: Patel Preksha M. - 21082221073
Vaghela Khushiba D. - 21082221096
Submitted To: Department of Computer Science
1
2 .EXISTING SYSTEM
 The existing system is that it is very difficult to retrieve data from case files.
 It is difficult to handle the whole system manually and it is less accurate and to keep the
data in case files for future reference because it may get destroyed.
 Moreover it is very difficult to retrieve data.
 Redundancy of data may occur and this may lead to the inconsistency. The manual
system is so time-consuming
2
3. NEED FOR NEW SYSTEM
 Efficiently maintains the details about the patient
 Simultaneously updates changes made to any data, item in the entire data base.
 It is faster than manual system
3
4. FUNCTIONAL SPECIFICATION
4.1 USER OF THE SYSTEM
1) Patient Module
2) Doctor Module
3) Admin Module
1.Patient Module
 Login
 Book Appointment
 History View Appointment
 Cancelation Option
2.Doctor Module
 Login
 view Appointment
 History View Appointment
3.Admin Module
 Login
 Doctor List
 Patient List
 Appointment Details
 Add Doctor
 Message
4
4.2 MODULE OF THE SYSTEM
Module Description/Activities Interacted Users
Login Authentication • Admin

• User
• Patient
Patient/Doctor Manage Patient/Doctor • Admin
View OR Book Manage Appointment • Admin

Appointment • Patient
• Doctor
5
5.SYSTEM REQUIREMENT
5.1 MINIMUM SOFTWARE REQUIREMENT
6
5.2 MINIMUM HARDWARE REQUIREMENT
7
6. SYSTEM FLOWCHAR
8
7. ER DIAGRAM
9
8.DATAFLOW DIAGRAM
8.1 ZERO LEVEL DFD (0.0)
10
8.2. FIRST LEVEL DFD – Admin
11
8.2. First LEVEL DFD – Patient
12
8.2. First LEVEL DFD – Doctor
13
9. DATA DICTIONARY
1.ADMIN LOGIN
No Field Name Data type Size Constraint Description
1 admin_username VARCHAR 50 NOT NULL Username of admin
2 admin_password VARCHAR 50 NOT NULL Set password
14
2.APPOINTMENTTB
1 Appointmen INT 11 PRIMARY KEY Id for appointment

t_id
2 pid INT 11 FORIGN KEY Id of Patient
3 fname VARCHA 20 NOT NULL First Name of Patient

R
4 lname VARCHA 20 NOT NULL Last Number of Patient

R
5 gender VARCHA 10 NOT NULL Gender of Patient

R
6 email VARCHA 30 NOT NULL Patient mail id

R
7 contact INT 10 NOT NULL Contact of Patient
8 doctor VARCHA 10 NOT NULL Name of doctor

R
9 docFees INT 5 NOT NULL Fees of doctor
10 appdate DATE NOT NULL Appointment date
11 apptime TIME NOT NULL Appointment time
12 userStatus INT 5 NOT NULL Status for appointment from user
15
13 doctorStatu INT 5 NOT NULL Status for appointment from

s doctor
16
3.DOCTB
1 Username VARCHAR 50 NOT NULL Username of

doctor
2 Password VARCHAR 50 NOT NULL Set password
3 Spec VARCHAR 20 NOT NULL Spec of doctor
4 Doc Fees INT 5 NOT NULL Fees of doctor
5 Email VARCHAR 50 NOT NULL Email of doctor
17
4.PATREG
1 pid INT 11 PRIMARY ID of Patient

KEY
2 fname VARCHAR 20 NOT NULL First Name of Patient
3 lname VARCHAR 20 NOT NULL Last Number of Patient
4 gender VARCHAR 10 NOT NULL Gender of Patient
5 email VARCHAR 30 NOT NULL Email of Patient
6 contact INT 10 NOT NULL Contact no of Patient
7 password VARCHAR 20 NOT NULL Set password
8 cpassword INT 20 NOT NULL Correct Password
18
5.PRESTB
1 Doctor VARCHAR 11 PRIMARY KEY Name of doctor
2 Pid INT 11 NOT NULL ID of Patient
3 Fname VARCHAR 20 NOT NULL First Number

of Patient
4 Lname VARCHAR 10 NOT NULL Last Number

of Patient
5 appdate DATE NOT NULL Date of

appointment
6 disease VARCHAR 100 NOT NULL Disease name
7 allergy VARCHAR 100 NOT NULL type of allergy
8 prescription VARCHAR 100 NOT NULL Prescription

Message
19
INPUT AND OUTPUT DESIGN
INPUT AND OUTPUT DESIGN FOR ADMIN SIDE REGISTRATITION PAGE | PATIENT
This is the log in page for admin where entering the right details they can manage site.
20
DASHBOARD | ADMIN
This is the Dartboard for admin here all the managing section available for admin.
21
DOCTOR LIST PAGE | ADMIN
In doctor section, admin can check the all the listed doctor on site.
22
PATIENT LIST PAGE | ADMIN
In patient section, admin can check the all the listed patient on site.
23
APPOINTMENT PAGE | ADMIN
In Appointment section, admin can check the all the booked appointments.
24
PRESCRIPTION PAGE | ADMIN
In Prescription section, admin can check the prescription given by doctor to patient on site.
25
ADD DOCTOR | ADMIN
In add doctor section, admin can also add some new doctor.
26
ADD DOCTOR | ADMIN REMOVE/DELETE DOCTOR |

ADMIN
In this section, admin can delete/remove the doctors.
27
QUERIES PAGE | ADMIN
In quires section, admin can check all the quires from patient on site.
section, admin can check all the quires from patient on sit
28
LOG IN | PATIENT
After registration this is the page where patient can log in themselves.
29
DASHBOARD | PATIENT
This is the Dashboard for patient there are some factions available.
30
BOOK APPOINTMENT PAGE | PATIENT
At book appointment section patient need fill up this form for book appoint doctor.
31
BOOK APPOINTMENT PAGE | PATIENT
And after the booked the appointment here is the conformation message.
32
APPOINTMENT HISTORY | PATIENT
In this appointment history section, patient can check booked appointment.
33
PRESCRIPTION PAGE | PATIENT
Prescription section where patient check update.
34
LOG IN PAGE | PATIENT
This is the log in page for doctor they need to fill up for entering there dashboard.
35
DASHBOARD | DOCTOR
After the verification process done here is the dashboard for the doctor.
36
APPOINTMENT VIEW PAGE | DOCTOR
In appointment section, doctor can check there daily appointments with patients.
37
PRESCIPTION | DOCTOR
In the prescription section, they would give update.
38
CONTACT US FORM
In contact us page, patient can send message to admin/contact to the admin.
39
Testing
Sr Test Scenario Test Cases

• Provider system should let us enter, edit
1) Access to providers system
and save the provider’s data
• It includes scenarios to enter different
2) Positive flow System Testing types of provider, change providers
details, save and inquire them
• Allows to save provider information with
incomplete data, contract’s effective date,
3) Negative flow System Testing
entering details about existing providers
in the system
• Validate the feed to members system,
finance system, claim system, and
4) System Integration Testing provider portal. Also, validate if the
changes from provider portal are entered
into the respective provider’s record
• Login and view providers details, claim
Positive flow providers portal status, and member details
5)
testing • Make change request to change the name,
address, phone number, etc.
• View the member details with an invalid
Negative flow providers portal
6) ID
testing
• Login with invalid credentials
• Login and view details about broker and
commission payment
7) Positive flow Broker portal testing
• Make a request to change the name,
address, phone number, etc.
Negative flow Broker portal • It should include scenarios to log in with
8)
testing invalid credentials
40
41
42
43
FUTURE ENHANCEMENT
Some are the expansion which we have thought of are:
•Try for to make system more user friendly.
•Improve search Facility.
•Admin can gives facility to the visitor which can see the status about organization’s all
information.
44
BIBLIOGRAPHY
 www.google.com
 https://chat.openai.com/
 https://www.darkcode.info/
 https://webdevtrick.com/
 http://www.onlinetutorialsweb.com/
 http://www.w3schools.com/
45
Thank You
46

Hsms

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Hsms

Uploaded by

Copyright:

Available Formats

A

B. Sc. (CA & IT) – V

TO WHOM SO EVER IT MAY CONCERN

Sr. No. Student Name Enrollment No.

1. Patel Preksha Manishkumar 21082221073

2. Vaghela Khushiba Dilipsinh 21082221096

Internal Guide Project Coordinator Program Coordinator Principal

Patel Preksha M. (21082221073)

This Hospital Management System project is a computerized hospital front desk

Sr. No. Particulars Page No.

Project Profile: Hospital Management System (PulsePower Suite):

Objective: The purpose of the Hospital Management System is a user-

Platform of Application: Web Site

Front End Tool: PHP , CSS , HTML , Java Script , Bootstrap

Back End Tool: MY SQL, PHP

Other Tool: Visual Studio Code

Project Duration: 90 Days

Internal Project Guide: Prof.Nishil Prajapati

Submitted By: Patel Preksha M. - 21082221073

Vaghela Khushiba D. - 21082221096

Submitted To: Department of Computer Science

3. NEED FOR NEW SYSTEM

 Efficiently maintains the details about the patient

 It is faster than manual system

4.1 USER OF THE SYSTEM

4.2 MODULE OF THE SYSTEM

Module Description/Activities Interacted Users

Login Authentication • Admin

Patient/Doctor Manage Patient/Doctor • Admin

View OR Book Manage Appointment • Admin

5.1 MINIMUM SOFTWARE REQUIREMENT

5.2 MINIMUM HARDWARE REQUIREMENT

8.1 ZERO LEVEL DFD (0.0)

8.2. FIRST LEVEL DFD – Admin

8.2. First LEVEL DFD – Patient

8.2. First LEVEL DFD – Doctor

No Field Name Data type Size Constraint Description

1 admin_username VARCHAR 50 NOT NULL Username of admin

2 admin_password VARCHAR 50 NOT NULL Set password

No Field Name Data type Size Constraint Description

1 Appointmen INT 11 PRIMARY KEY Id for appointment

2 pid INT 11 FORIGN KEY Id of Patient

3 fname VARCHA 20 NOT NULL First Name of Patient

4 lname VARCHA 20 NOT NULL Last Number of Patient

5 gender VARCHA 10 NOT NULL Gender of Patient

6 email VARCHA 30 NOT NULL Patient mail id

7 contact INT 10 NOT NULL Contact of Patient

8 doctor VARCHA 10 NOT NULL Name of doctor

9 docFees INT 5 NOT NULL Fees of doctor

10 appdate DATE NOT NULL Appointment date

11 apptime TIME NOT NULL Appointment time

12 userStatus INT 5 NOT NULL Status for appointment from user

13 doctorStatu INT 5 NOT NULL Status for appointment from

No Field Name Data type Size Constraint Description

1 Username VARCHAR 50 NOT NULL Username of

2 Password VARCHAR 50 NOT NULL Set password

3 Spec VARCHAR 20 NOT NULL Spec of doctor

4 Doc Fees INT 5 NOT NULL Fees of doctor

5 Email VARCHAR 50 NOT NULL Email of doctor

No Field Name Data type Size Constraint Description

1 pid INT 11 PRIMARY ID of Patient

2 fname VARCHAR 20 NOT NULL First Name of Patient

3 lname VARCHAR 20 NOT NULL Last Number of Patient