Professional Documents
Culture Documents
On
“Hospital Management System”
In partial fulfillment for the award of the degree
Of
BACHELOR OF COMPUTER APPLICATION
[B.C.A]
Year 2023-2024
SUBMITTED BY: GUIDED BY:
Jaimish Narola Prof. Bipin Jadhav
Fenil Rokad
Harsh Nakrani
BCA-6th SEMESTER
Submitted to:
First and foremost, we extend our sincere appreciation to our project guide,
Prof. Bipin Jadhav, for his invaluable guidance, unwavering support, and
insightful feedback throughout every stage of this endeavor. His expertise and
encouragement have been instrumental in shaping our project and enhancing
our understanding of the subject matter.
Additionally, we extend our thanks to our classmates and friends for their
encouragement, feedback, and assistance in various aspects of this project.
Finally, we would like to express our gratitude to our families for their patience,
understanding, and unwavering support throughout this journey.
This project would not have been possible without the collective efforts and
support of all those mentioned above.
Thank You.
INTRODUCTION
Project Profile
Project Title
Our project is not only aimed at improving the efficiency and effectiveness of
hospital operations but also at enhancing the overall patient experience. By
automating routine tasks, reducing paperwork, and ensuring timely access to
critical information, our Hospital Management System empowers healthcare
providers to focus more on delivering high-quality care to patients.
In collaboration with our project guide, Prof. Bipin Jadhav, and leveraging the
latest technologies, we have endeavored to create a robust and scalable solution
that meets the evolving needs of healthcare organizations. Through this project,
we aspire to contribute to the advancement of healthcare management practices
and ultimately, to the betterment of patient care.
Aims & Objectives
Aims:
1.Enhance Operational Efficiency: Develop a user-friendly Hospital
Management System (HMS) website to streamline administrative tasks and
enhance operational efficiency. This system aims to automate routine processes,
reduce paperwork, and improve overall workflow management within
healthcare facilities.
Objectives:
1. User-Friendly Interface: Design and implement an intuitive user interface
using HTML, CSS, JavaScript, and Bootstrap to ensure ease of use and
accessibility for healthcare professionals and administrators.
2.Robust Back-End System: Develop a robust back-end system with SQL
Server and PHP to handle data storage, retrieval, and processing securely. This
includes designing efficient database schemas, writing optimized SQL queries,
and implementing server-side logic to ensure smooth system operation.
4.Doctor Management: Include features for doctor and staff management, such
as profiles, scheduling, and performance tracking. This requires designing
administrative interfaces for managing user accounts, assigning roles and
permissions, and tracking staff activities.
Client Side:
RAM
Operating System
Browser
Server Side:
RAM
Disk Space
Operating System
Server
Documentation Tools
MS-Word
Features Of PHP:
Large Standard Library and Ecosystem: PHP comes with a large standard
library and has a rich ecosystem of frameworks, libraries, and content
management systems (CMS) that streamline web development tasks. This
extensive ecosystem accelerates development, reduces the need for reinventing
the wheel, and facilitates the creation of robust and feature-rich web
applications.
Xampp Server:
XAMPP helps a local host or server to test its website and clients via computers
and laptops before releasing it to the main server.
MySQL:
Security: MySQL provides robust security features to protect data integrity and
confidentiality. This includes access control mechanisms, encryption support,
and secure communication protocols like SSL/TLS, ensuring that sensitive data
is protected from unauthorized access and manipulation.
JavaScript:
Client-Side Execution: JavaScript runs on the client side of the web, allowing
it to be used for tasks such as data validation, form submission, and creation of
interactive effects without requiring server-side processing.
CSS:
Styling Web Pages: CSS is used to style the visual presentation of web pages,
including elements such as text, colors, fonts, backgrounds, and layout.
Selectors and Declarations: CSS uses selectors to target HTML elements and
declarations to specify the styling properties of those elements, allowing for
precise styling control.
Responsive Design: CSS enables the creation of responsive web designs that
adapt to different screen sizes and devices, ensuring optimal user experience
across devices.
HTML:
Requirement Analysis:
- Conduct a thorough analysis of requirements by interviewing stakeholders,
reviewing existing processes, and studying similar systems.
- Document functional requirements, such as patient registration, appointment
scheduling, medical record management, billing, and reporting.
- Identify non-functional requirements, including performance, scalability,
security, and usability criteria.
Flexibility Study:
- Assess the flexibility of the proposed system to accommodate future changes
and enhancements.
- Consider factors such as evolving business requirements, technological
advancements, and regulatory changes that may impact the system's long-term
viability.
- Design the system with scalability, modularity, and extensibility in mind to
facilitate future updates and expansions.
Requirement Analysis:
1.Define Project Scope: Begin by clearly defining the scope of your college
project. Consider the functionalities and features that you aim to include in the
hospital management system. This might involve functionalities like patient
registration, appointment scheduling, doctor management, and basic inventory
tracking.
2.Identify User Roles: Identify the different types of users who will interact
with the system. This typically includes administrators, doctors, and patients.
Understand the specific needs and responsibilities of each user role to ensure
that the system caters to their requirements effectively.
Data Gathering:
1. Identify Sample Data: Gather sample data that can be used to populate the
system during development and testing. This could include mock patient
records, appointment schedules, and inventory items. Ensure that the sample
data is representative of real-world scenarios but simplified for the scope of
your project.
2.Understand Data Structure: Take the time to understand the structure and
format of the sample data. This will inform the design of your database schema
and help you develop data entry forms and interfaces that align with the data
requirements of your project.
3.Determine Data Needs: Determine the specific data needs of your project
based on the identified requirements. Focus on capturing the data that is
essential for demonstrating the core functionalities of the hospital management
system. This may include patient demographics, medical history, appointment
details, and inventory information.
4. Data Mapping: Map the sample data to the corresponding data entities and
attributes in your database schema. This ensures that your system captures and
utilizes the necessary data effectively. Pay attention to data relationships and
dependencies to maintain data integrity and consistency.
5.Data Privacy and Security: While data privacy and security may not be as
critical for a college project as they would be in a real-world system, it's still
important to consider basic measures to protect sensitive information. This
could include anonymizing patient data and implementing access controls to
restrict unauthorized access to the system.
Flexibility Study
Feasibility study plays very important role in the development of any system,
but when it is the case of development of any software then its importance
increases much more because in the case one should be very clear about
availability of the time and resources. Before starting the development of the
software one should give considerable amount of time for feasibility study
because the successful completion of project depends upon feasibility.
The feasibility of our project has been judged on the basis of time, technology,
resources available and project length.
Time:
This project takes at least 3 month to be completed if we take help of
reused components otherwise it will take 6 months to be completed.
We will not make use of components and therefore will be able to
complete the project in 6 months. Thus according to time the feasibility is not
that right.
Technology:
The necessary technology, viz., front-end development tool, back-end
database technology and various other tools namely installation tools, etc. for
developing the system, are already available within the organization. So this
problem is feasible.
Resources:
We need good knowledge software engineers and practitioners. We need
Net connection. We have all the resources in the desired amount.
Project Size:
The Project size might be large line of code. This is just the rough
assumption because we don’t have any basis of the past projects.
Thus the project overall feasibility is normal and therefore we have undertaken
this project.
System Model Architecture
Flow Chart
DFD
ER Diagram
Flow Chart
DFD
DFD typically stands for "Data Flow Diagram." It's a graphical representation
of the flow of data within a system, illustrating how data moves through
processes, stores, and external entities.
Elements of DFD
External Entity
Process:
Data Flow:
Data Store:
Data Source/Sink:
External Entities:
Processes:
Data Flows:
Data flows represent the movement of data between various elements of the
system. They are depicted as arrows and indicate the direction of data
movement from one element to another. Data flows show how data is input into
the system, processed, and output from the system.
Data Stores:
Data stores represent the places where data is held within the system. They can
be physical locations like databases or files, or they can represent temporary
storage within the system's memory. Data stores are depicted as parallel lines.
These are special types of external entities that either produce data into the
system (sources) or consume data from the system (sinks). They are similar to
regular external entities but have a specific role in data flow.
Zero level
First level
Second level
ER Diagram
Table Structure
Admin Table
Name Data Type Size Constrain
username varchar 50 Not null
password Varchar 50 Not null
Appointment Table
Name Data Type Size Constrain
pid int 11 Not null
ID int 11 Primary key
fname varchar 20 Not null
iname varchar 20 Not null
gender varchar 10 Not null
email varchar 30 Not null
contact varchar 10 Not null
doctor varchar 30 Not null
docfees int 5 Not null
appdate date - Not null
apptime time - Not null
userstatus int 5 Not null
doctorstatus int 5 Not null
Blog Table
Name Data Type Size Constrain
id int 5 Primary key
subject varchar 75 Not null
description varchar 1500 Not null
image1 varchar 60 Not null
Contact Table
Name Data Type Size Constrain
name varchar 30 Not null
email text - Not null
contact varchar 10 Not null
message varchar 200 Not null
subject varchar 50 Not null
time varchar - Not null
id int 5 Primary key
Doctor Table
Name Data Type Size Constrain
username varchar 50 Not null
password varchar 50 Not null
email varchar 50 Not null
spec varchar 50 Not null
docfees int 10 Not null
image1 varchar 50 Not null
id int 5 Primay key
Gallery Table
Name Data Type Size Constrain
id int 5 Primary key
heading varchar 50 Not null
image1 varchar 255 Not null
Health Package Table
Patient Table
Name Data Type Size Constrain
pid int 11 Primary key
fname varchar 20 Not null
lname varchar 20 Not null
gender varchar 10 Not null
email varchar 30 Not null
contact varchar 10 Not null
password varchar 30 Not null
cpassword varchar 30 Not null
Prescription Table
Name Data Type Size Constrain
doctor varchar 50 Not null
pid int 11 Not null
id int 11 Not null
fname varchar 50 Not null
lname varchar 50 Not null
appdate date - Not null
apptime time - Not null
disease varchar 250 Not null
allergy varchar 250 Not null
prescription varchar 1000 Not null