DURGAPUR INSTITUTE OF MANAGEMENT AND

SCIENCE

A MINOR PROJECT ON

E-HEALTH CARE SYSTEM

Submitted By:-

Name – Tanusri Gorai

University Roll- 32401222072
Registration no- 223241010084

Group member
1. Animesh Pandir 32401222069

2. Nikita Pandit 32401222081

Subject Name : Industrial Traning And Minor Project

Subject code : BCAD581

Under the guidance of

Mrs. Rajashree Jash
Asst.Professor

1|Page
 DURGAPUR INSTITUTE OF MANAGEMENT AND SCIENCE
Formally known as Bengal College of Engineering and Technology

CERTIFICATE OF GUIDE

This is to certify that the project entitled:

E-HEALTH CARE SYSTEM

Has been completed successfully By Tanusri Gorai, BCA 5th semester.

DURGAPUR INSTITUTE OF MANAGEMENT AND SCIENCE BidhanNagar,Durgapur-713212

Guide Principal
Mrs. Rajashree Jash Mam Dr. Praveen Kumar
Singh Sir

2|Page
 ACKNOWLEDGEMENT
Apart from the efforts of team, the success of any project
depends largely on the encouragement and guidelines of
many others. We take this opportunity to express our
gratitude to the people who have been instrumental in the
successful completion of this project.
The completion of any inter-disciplinary project depends upon
cooperation, co-ordination and combined efforts of several
sources of knowledge.
We are eternally grateful to our teacher Rajashree Jash for
her even willingness to give us valuable advice and direction
under which we executed this project. Her constant guidance
and willingness to share her vast knowledge made us
understand this project and its manifestations in great depths
and helped us to complete the assigned tasks.

Tanusri Gorai
Roll no - 32401222072

3|Page
 CONTENTS

1. Certificate of guide

2. Acknowledgement

3. Content

4. Preface

5. Project Identification

6. Process Model

7. Introduction

8. Software Requirment and Specification

9. Design

10. Screenshot and codes

11. Future Scope

12.Conclusion

13. Reference

4|Page
 PREFACE
Welcome to the HMS / Hospital Management System, a
comprehensive and intuitive solution designed to
revolutionize the way healthcare institutions manage their
operations, streamline processes, and enhance patient care.
In an era where efficiency and accuracy are paramount in
delivering quality healthcare services, our system stands as a
beacon of innovation.

Our Hospital Management System is meticulously crafted to

meet the diverse needs of healthcare professionals,
administrators, and patients alike. With a focus on seamless
integration and user-friendly interfaces, we aim to empower
hospitals to achieve optimal operational efficiency and
provide patients with a heightened level of care.

Key Features:

Doctor , Nurse & Patient Login

Appointment Scheduling

Contact Option

Specialist Doctor List

User-Friendly Interface

5|Page
PROJECT IDENTIFICATION
In this busy world we don’t have the time to wait in infamously long hospital queues.
The problem is, queuing at hospital is often managed manually by administrative staff,
then take a token there and then wait for our turn then ask for the doctor and the most
frustrating thing - we went there by traveling a long distance and then we come to know
the doctor is on leave or the doctor can’t take appointments.

HMS will help us overcome all these problems because now patients can book their
appointments at home, they can check whether the doctor they want to meet is
available or not. Doctors can also confirm or decline appointments, this help both
patient and the doctor because if the doctor declines’ appointment then patient will
know this in advance and patient will visit hospital only when the doctor confirms’ the
appointment this will save time and money of the patient.HMS is essential for all
healthcare establishments, be it hospitals, nursing homes, health clinics, rehabilitation
centers, dispensaries, or clinics. The main goal is to computerize all the details regarding
the patient and the hospital. The installation of this healthcare software results in
improvement in administrative functions and hence better patient care, which is the
prime focus of any healthcare unit.

Benefits of implementing a hospital management system:

 Appointment booking
o Helps patients cut the long queue and saves their time
o Is equipped with features like automated email and text message
reminders

6|Page
 Overall cost reduction
o Cuts down paper costs as all the data are computerized
o No separate costs for setting up physical servers

 Data accuracy
o Removes human errors
o Alerts when there’s a shortage of stock

 Data security
o Helps to keep patients records private
o Restricts access through role-based access control

 Revenue management
o Makes daily auditing simple
o Helps with statistics and other financial aspects

7|Page
 PROCESS MODEL

Hospital Management System follows INCREMENTAL MODEL because

initially software requirements are reasonably well defined but the overall
scope of development effort is a purely linear process. There may be other
requirements of the user which will be known later. So, those requirements
can the implemented and delivered in the following next increments.

Creating a process model for your Hospital Management System (HMS)

website using the MERN stack (MongoDB, Express.js, React.js, Node.js)
involves identifying and visualizing the key processes your system will
manage. Below is an outline of a Process Model:

Process Model for Hospital Management System

1. Admin
o Manage users (Doctors, Patients, Staff).
o Manage hospital resources (appointments, facilities).
o View reports and analytics.
2. Doctors
o View schedules and appointments.

3. Patients
o Book appointments.
o Manage profiles .

8|Page
 CHAPTER 1
INTRODUCTION
1.1 PURPOSE
1.2 SCOPE
1.3 DEFINITIONS and ABBREVIATIONS
1.4 OVERVIEW

9|Page
1.1 PURPOSE

This software will help the hospitals or clinic to be more efficient in registration of their
patients and manage appointments, records of patients. It enables doctors and admin to
view and modify appointments schedules if required. The purpose of this project is to
computerize all details regarding patient details and hospital details.

1.2 SCOPE

The system will be used as the application that serves hospitals, clinic, dispensaries or
other health institutions. The intention of the system is to increase the number of
patients that can be treated and managed properly.
If the hospital management system is file based, management of the hospital has to put
much effort on securing the files. They can be easily damaged by fire, insects and
natural disasters. Also could be misplaced by losing data and information.

1.3 DEFINITIONS and ABBREVIATIONS

1. Cardiologist - treats heart disease.

2. Pediatrician - treats infants, toddlers, children and teenagers.
3. Plastic Surgeon - restores, reconstructs, corrects or improves in the shape and
appearance of damaged body structures, especially the face.
4. Psychiatrist - treats patients with mental and emotional disorders.
5. Ophthalmologist - treats eye defects, injuries, and diseases
6. ENT- Ear, Nose and Throat Specialist.

 Appt – Appointment.
 Sign up - Creating New User.
 Log in - Logging in Existing User.
 PhNo - Mobile number.
 Addr – Address.
Expr – Experience.

10 | P a g e
1.4 OVERVIEW

Our application contains two modules – the admin module and the user module.
Our application will not only help the admin to preview the monthly and/or yearly
data but it will also allow them to edit, add or update records. The software will
also help the admin to monitor the transactions made by the patients and
generate confirmations for the same. The admin will be able to manage and
update information about doctors.
The user module can be accessed by both the doctors and the patients. The
doctor can confirm and/or cancel appointments. The doctors can even add
prescriptions for their patients using our application. The patients will be able to
apply for the appointment and make transaction for the same, and can even
cancel appointments with the doctors. They can track details about the previous
transactions made by them.

Advantages

 The system automates the manual procedure of managing hospital activities.

 Doctors can view their patients’ treatment records and details easily.
 It even generates an instant bill.
 The system is convenient and flexible to be used.
 It saves their time, efforts, money and resources.

Disadvantages

 Requires large database.

 The admin has to manually keep updating the information by entering the details
in the system.
 Need Internet connection.

11 | P a g e
 CHAPTER 2
SOFTWARE REQUIREMENT
SPECIFICATION
2.1 Product Perspective
2.1.1 System Interfaces
2.1.2 System Specifications
2.1.2.1 H/W Requirement
2.1.2.2 S/W Requirement
2.2 Product functions
2.3 Data Flow Diagram (DFD)
2.3.1 Context Level Diagram
2.3.2 DFD Level – 1
2.3.3 DFD Level – 2
2.4 Use Case Diagram
2.5 Use Case Description

12 | P a g e
2.1 Product Perspective

This Hospital Patient Info Management System is a self-contained system that manages
activities of the hospital.
Due to improperly managed details medical center faces quite a lot of difficulties in
accessing past data as well as managing present data. The fully functional automated
hospital management system which will be developed through this project will eliminate
the disadvantages caused by the manual system by improving the reliability, efficiency
and performance. The usage of a database to store patient, employee, stock details etc.
will accommodate easy access, retrieval, and search and manipulation of data. The
access limitations provided through access privilege levels will enhance the security of
the system. The system will facilitate concurrent access and convenient management of
activities of the medical center.

2.1.1 System Interfaces

 User Interfaces
 This section provides a detailed description of all inputs into and outputs from
the system. It also gives a description of the hardware, software and
communication interfaces and provides basic prototypes of the user interface.
 The protocol used shall be HTTP.
 The Port number used will be 80.
 There shall be logical address of the system in IPv4 format.

 Hardware Interfaces
 Laptop/Desktop PC-Purpose of this is to give information when Patients ask
information about doctors, medicine available lab tests etc. To perform such
Action it need very efficient computer otherwise due to that reason patients
have to wait for a long time to get what they ask for.
 Laser Printer (B/W) - This device is for printing patients’ info etc.
 Wi-Fi router - Wi-Fi router is used to for internetwork operations inside of a
hospital and simply data transmission from pc’s to sever.

13 | P a g e
 2.1.2 System Specifications

2.1.2.1 H/W Requirement

> Core i5 processor
> 2GB Ram.
> 20GB of hard disk space in terminal machines
> 1TB hard disk space in Server Machine

2.1.2.2 S/W Requirement

>Windows 7 or above operating system
>VS Code
> Node.js
> MongoDB
>React

2.2 Product functions

o Provide access to registered users only.

o Registration of new patients.
o Enable patient to view their record.
o Enable patient to update their record.
o Generate appointment date and timing.
o Confirmation by doctor.
o Patients can do Payment.
o Modification in schedule by patient.
o Admin access to patient’s record.
o Admin Verify Payment and Generate Bill/Receipt.
o Admin can view monthly/yearly records.

14 | P a g e
2.3 DATA FLOW DIAGRAM (DFD)

Health Care system

15 | P a g e
Level 1- DFD

16 | P a g e
2.4 USE CASE DIAGRAM

17 | P a g e
 2.5 USE CASE DESCRIPTION
Use Case 1: Login
 Actor(s): Patient, Doctor, Nurse, Admin
 Description: Allows users to log in to the system.
 Main Flow:
1. The user provides a username and password.
2. The system validates the credentials against the MongoDB Users collection.
3. Upon successful authentication, the user is granted access to the system.
 Extensions:
o If authentication fails, an error message is displayed.
o Forgotten password flow can be initiated.

Use Case 2: Book Appointment

 Actor(s): Patient
 Description: Patients can book appointments with doctors.
 Main Flow:
1. The patient selects a doctor and available time slot.
2. The system checks availability in the Appointments collection.
3. If available, the appointment is confirmed and stored.
4. A confirmation is displayed to the patient.
 Extensions:
o If the slot is unavailable, the patient is prompted to choose another time.

Use Case 3: View Appointment

 Actor(s): Patient, Doctor
 Description: Patients and doctors can view their scheduled appointments.
 Main Flow:
1. The user requests to view their appointments.
2. The system retrieves the data from the Appointments collection.
3. The list of appointments is displayed.
 Extensions:
o If no appointments are found, the system displays a relevant message.

Use Case 4: Update Appointment

 Actor(s): Doctor
 Description: Doctors can update or reschedule appointments.
 Main Flow:
1. The doctor selects an appointment to update.
2. The system retrieves the appointment details.
3. The doctor updates the details (e.g., time, date).
18 | P a g e
 4. The system saves the changes in the Appointments collection.
 Extensions:
o If the new slot is unavailable, an error message is shown.

Use Case 5: View Patient Details

 Actor(s): Doctor, Nurse
 Description: Doctors and nurses can view patient details.
 Main Flow:
1. The user requests to view a specific patient's data.
2. The system retrieves the patient data from the Patient Records collection.
3. The details are displayed.
 Extensions:
o If no records are found, an appropriate message is displayed.

Use Case 6: Update Patient Data

 Actor(s): Nurse
 Description: Nurses can update patient information.
 Main Flow:
1. The nurse selects a patient to update.
2. The system retrieves the existing data.
3. The nurse makes updates to the data (e.g., address, contact).
4. The system saves the updated data in the Patient Records collection.
 Extensions:
o If the update fails, the nurse is notified.

Use Case 7: Update Diagnosis

 Actor(s): Doctor
 Description: Doctors can add or update diagnoses for patients.
 Main Flow:
1. The doctor selects a patient.
2. The system retrieves the patient's medical record.
3. The doctor updates the diagnosis and adds treatment plans.
4. The updated data is stored in the Patient Records collection.
 Extensions:
o If the save operation fails, the system prompts an error.

19 | P a g e
 CHAPTER 3
DESIGN

4.1 ER DIAGRAM
4.2 Entities and Attribute

20 | P a g e
4.1 ER DIAGRAM

21 | P a g e
Entities and Attributes
1. Patient
o Attributes:
 PatientID: A unique identifier for each patient.
 Name: The name of the patient.
 Age: The patient's age.
 Gender: The patient's gender.
 Contact: The patient's phone number or email.
 Address: The patient's home address.
 LoginID: The patient's login credentials for accessing the
system.
2. Doctor
o Attributes:
 DoctorID: A unique identifier for each doctor.
 Name: The name of the doctor.
 Specialization: The doctor's area of expertise (e.g.,
cardiology, neurology).
 Contact: The doctor's phone number or email.
 LoginID: The doctor's login credentials for accessing the
system.
3. Nurse
o Attributes:
 NurseID: A unique identifier for each nurse.
 Name: The name of the nurse.
 Department: The department in which the nurse works
(e.g., emergency, pediatrics).
 Contact: The nurse's phone number or email.
 LoginID: The nurse's login credentials for accessing the
system.
4. Admin
o Attributes:
 AdminID: A unique identifier for each admin.
 Name: The name of the administrator.
 Contact: The admin's phone number or email.

22 | P a g e
  LoginID: The admin's login credentials for accessing the
system.
5. Appointment
o Attributes:
 AppointmentID: A unique identifier for each
appointment.
 Date: The date of the appointment.
 Time: The time of the appointment.
 Status: The status of the appointment (e.g., scheduled,
completed, canceled).
 PatientID: A reference to the Patient who made the
appointment.
 DoctorID: A reference to the Doctor who will attend the
patient.
6. User (Common to all actors)
o Attributes:
 UserID: A unique identifier for the user.
 Role: The role of the user (e.g., Patient, Doctor, Nurse,
Admin).
 Email: The user's email address.
 Password: The user's password for authentication.

Relationships Between Entities

1. Patient - Appointment:
o A Patient can have multiple Appointments (1-to-many
relationship). A patient can book many appointments, but
each appointment is specific to one patient.
2. Doctor - Appointment:
o A Doctor can have multiple Appointments (1-to-many
relationship). A doctor can attend multiple appointments,
but each appointment is assigned to only one doctor.
3. Nurse - Patient:
o A Nurse may assist or manage patient care. Nurses help
update patient information but don’t own appointments
23 | P a g e
 directly. This is typically a 1-to-many or many-to-many
relationship.
4. Admin - User Management:
o The Admin has control over the User entities (which include
Patient, Doctor, Nurse, and Admin). Admins can add,
remove, or modify users. The relationship is typically one-to-
many (1 Admin to many Users).
5. User - Role:
o A User can have one of several roles (Patient, Doctor, Nurse,
Admin). The role determines the functionality and data
access level within the system. It is a 1-to-1 relationship.

24 | P a g e
 CHAPTER 4

Screenshot&Code

25 | P a g e
Home Page

26 | P a g e
 Login pages
In our HMS all user have different login
option that makes our webpage a user
friendly and easy to use webpage

FOR PATIENT

27 | P a g e
FOR DOCTOR

28 | P a g e
Separate Appointment option
FOR NURSE

29 | P a g e
Separate Specialist Doctor section

This section help pataints to select the best doctors ,because our main motive was to provide best
experience and treatment

30 | P a g e
Contact Us

31 | P a g e
About us

32 | P a g e
DATABASE

33 | P a g e
 Chapter-5

Futures and Scope

34 | P a g e
1. Enhanced Patient Features
 Patient Notifications:
o Integration of SMS or email alerts for appointment reminders and updates.
 Health Tracking:
o Allow patients to upload and maintain basic health records (e.g., blood
pressure, sugar levels) for better consultation preparation.

2. Doctor and Nurse Tools

 Medical History Access:
o Enable doctors to view a patient's complete medical history, including lab
results and external consultations.
 Shift Management:
o Provide scheduling tools for nurses and doctors to manage shifts and
workload effectively.

3. Online Communication
 Telemedicine Integration:
o Add options for virtual consultations via video conferencing tools.
o Secure chat features for follow-up communication between doctors and
patients.
 Prescription Uploads:
o Allow patients to upload prescriptions from offline visits for tracking and
better record management.

4. Data Analytics and Reporting

 Appointment Trends:
o Analyze and display data such as peak appointment times or most-visited
departments.
 Performance Metrics:
o Generate reports on the efficiency of doctors, nurses, or overall hospital
operations.
 Patient Feedback System:
o Collect and analyze feedback for continuous improvement in patient care
and experience.
35 | P a g e
5. Scalability and Multi-Hospital Support
 Multi-Hospital Management:
o Expand the system to support multiple hospitals, with centralized and
decentralized data management options.
 Cloud Integration:
o Transition the system to cloud platforms for enhanced performance,
scalability, and disaster recovery.

6. Enhanced Security Features

 Role-Based Permissions:
o Add more granular access controls for different roles and tasks.
 Audit Logs:
o Maintain logs of all actions performed in the system for accountability and
compliance.
 Data Encryption:
o Implement end-to-end encryption for all sensitive data transactions .

36 | P a g e
 CONCLUSION
Working on the project was an excellent experience. It helped us to understand the importance of
planning, designing and implementation so far we have learnt in our theory books. It helped us
unleashing our creativity while working in a team. It also realized the importance of team working,
communication as a part of this project. The project was successfully completed after a lot of
efforts and work hours. This project underwent number of compiling, debugging, removing errors,
making it bug free, adding more facilities in Hospital Management System and interactivity making
it more reliable and useful. This project focused that scheduling a project and adhering to that
schedule creates a hard sense of time- management. It has also let us known that co-operative
teamwork always produce effective results. The entire project has been developed and deployed
as per the requirements stated by the user.
There are also few features which can be integrated with this system to make it more flexible.
Below list shows the future points to be consider :
• Book appointment at any time.
• Including a different doctor section.
• Contact us section.
Finally, we like to conclude that we put all our efforts throughout the development of our project
and tried to fulfill most of the requirements of the user.

37 | P a g e
REFERENCES
 www.google.com
 YOUTUBE
 GeeksforGeeks

38 | P a g e
Thankyou

39 | P a g e