Chapter 3,4,5 (2)
Chapter 3,4,5 (2)
The Hospital Emergency Management System is structured around three primary user roles:
Patient, Doctor, and Administrator (Admin). The workflow begins with the Patient
completing a registration process via a secure user registration form. Upon successful login, the
Patient is granted access to a structured emergency request form designed to capture key details
such as symptoms, urgency level, and personal information. Once submitted, each emergency
request is stored in the database and automatically prioritized based on predefined urgency
parameters, ensuring timely attention by medical personnel.
A comprehensive system analysis phase was conducted through direct engagement with
healthcare stakeholders to identify practical challenges encountered in managing emergency
appointments and patient data. Insights gathered informed the development of a solution
architecture that prioritizes data integrity, minimizes redundancy, and promotes high system
availability. The design approach emphasized a user-centered interface to enhance usability
and adoption across medical staff and patients alike. The choice of PHP for backend logic and
MySQL for data persistence was driven by their proven reliability, scalability, and compatibility
with healthcare infrastructure.
The Doctor's interface features a real-time dashboard that displays emergency alerts as they are
received. Doctors can view detailed case information, acknowledge emergency requests, and
update patient treatment statuses accordingly. The Admin interface serves as the central control
unit, enabling the creation of tenders (e.g., scheduling slots or service windows), assignment of
doctors to cases, and evaluation of patient bids based on medical and logistical criteria. Every
action within the system is meticulously timestamped and logged, providing a comprehensive
audit trail for transparency, accountability, and continuous monitoring.
doctor's website, or simply, and patients can easily arrange appointments via the online
software. Patients can also supply the doctor with extra information, give the doctor a
sense of their position and allow the physician the opportunity to prepare the information
essential for the arrival of patients. A scheduling system enables individuals to arrange
their appointments online comfortably and securely. The web-based appointment system
may greatly boost registration satisfaction and successfully decrease the total waiting
time compared with the typical queuing approach. Time to wait Waiting time refers to the
time a patient has to wait for a specific step after this activity is initiated or requested. It is
defined as "the time it lasted from the moment the patient attended the outpatient clinic
when the patient was really prescribed. The overall time spent by a patient from
programming language on the server utilized for data development and transmitting via
The data gathered in the research came from the main sources and other data sources,
premium Microsoft Encarta, seminars, conferences and personal research. The data was
The current situation is examined with the available data before the timetable is
optimized. The performance of the schedule, length of appointment, current waiting times
and no shows are examined. This analysis is hospital informative. It also determines the
most important weekly sessions that allow the study to focus on those weekly sessions.
Finally, these results provide the major reasons for the period of waiting, so that
Hospitals now use a manual appointment system. The existing system involves many
paper forms, with data shops dispersed over the infrastructure for hospital management.
Information is often incomplete or does not comply with the norms of management.
information is lost are commonly lost in transit between departments. In the hospital there
are several copies of the same information and data in various data stores may be
inconsistent.
The hospital appointment system is meant to replace your present manual paper system in
any institution. The new system is designed to monitor patient information. Time and
date book appointment with the doctor, meeting objective, etc. These services must be
delivered in an efficient and cost-effective manner in order to reduce the time and
The following are required to effectively carry out this project, which majorly is the
Implementation is now provided by The PHP Group and initially developed by Danish-
Canadian programmer
which allows you to create WordPress off-line site, on a local web server, on your PC.
This easy and easy to use solution works on Windows, Linux and Mac - the cross-
platform component
This work has been based on a modified waterfall model. It was reduced to five different
phases rather than the six major phases of the waterfall model. This is because all needs
have been known and the aim of our software development is to computerize/automate an
WATERFALL MODEL
1. Analysis
3. Design
4. Implementation
5. Post-Implementation
This is a straighter approach to waterfall. The analysis begins. The following stage, the
evaluation and selection phase of the tool can be used once this phase is done. This
methodology differs from the waterfall model since the design phase is implemented
differently than usual and a development phase is not required as the product is existent.
Instead of designing the system itself, the design phase is concerned further with
integrating the product with existing infrastructure and how the system is filled in.
Analysis phase
During the analysis phase, the high-level needs, aims and objectives of the Hospital will
be identified and the requirements for the hospital will be obtained. In this phase the
needs for the Hospital appointment scheduling system will be made evident. During this
phase, interviews, observations and collecting of pertinent documents were done. At the
done. At the end of this phase a complete functional requirements specification, which
outlines all facets of the system were developed. A series of profiles, which will
document the information acquired, which helps not only the functional requirements
specification but also the tool selection and design phase will also be developed. The
a. Organization profile
b. Document profile(s)
c. User profile(s)
Use diagrams of case The aim of the case diagramming technique for waterfalls is to
consider and design the dynamical aspects of a system that help to gather needs while
also identifying the external and internal factors influencing the system and showing the
particular. This method defines a system to meet its needs by specifying the architecture,
components, modules, interface, and data. A solid and dependable database for efficient
collecting and processing of data is the main feature considered in designing the new
system. The system also aims to provide specifications which enable the new system to
be fully implemented, accurately and specifically. After a careful review of the existing
system the replacement system was designed. The design is a solution that translates
demands in ways that meet them The design of the system comprises three levels: the
DESIGN GOAL
The objective of the design is to create a user-friendly application with full functionality
for registration activities, login, patient appointment reservations, doctoral response and
START
LOGIN PAGE
If correct
Book Appointment
Doctor’s feedback
End program
6 Microsoft Azure
DATABASE DESIGN
is an inter-related, minimum redundancy data collection which can swiftly and efficiently
serve multiple consumers. Its aim is to make it easy, fast and adaptable for the user to get
addresses an organization's current and future information storage needs. Its objective is
to improve current conditions. By accepting input from the existing system, the new
The structure and relationships of the patient database appointment were designed on a
functional basis. We used data from a relational MySQL database to store different
booing aims, history and patient investigation. We utilized MySQL Workbench, a visual
tool for data modelling and SQL databases development, to design and implement the
3.5 CODING
The system coding was done with PHP and JavaScript, basically, the MySQL server and
SQL database language were combined in PHP and the other interactive elements of the
programme. the backend was achieved. The system is also used in the front-end
programming languages with HTML, CSS and Bootstrap. The Code weighs only 5 MB
The websites consist mainly of dynamic web pages. Dynamic indicates that the user
interacts more and more with the website, and the site responds accordingly after only
reading the pages. Usually, a web server offers the built-in and host web pages, the IP
address and the domain name of a server. A total of 26 pages from the PHP home page,
the Doctors' website, the Notepad++ Text Editor, providing both PHP, HTML, and CSS
CHAPTER FOUR
Additional Enhancements:
During implementation, rigorous testing was performed to ensure system stability and usability
across multiple devices and browsers. Additional functionalities such as email notification for
booked appointments, data encryption for patient confidentiality, and real-time appointment
status tracking were integrated. The system was also modularized to ease future scalability and
maintenance. Interface components were designed with accessibility in mind, accommodating
users with varying levels of digital literacy.
The logout functionality ensures session security and is available for both Admin and
Patient dashboards. All forms, including create report, registration, and bid submission,
were validated server-side using PHP and sanitized to prevent SQL injection. The bid
performance module compares the user's bid to others and gives a ranking based on
percentage and total submitted amount.
4.1 SYSTEM IMPLEMENTATION
Two main components – Front end and Backend – consist of the proposed software
system. For designing of the front end or interface of the system, HTML and CSS (client
side) are employed. HTML is the Hypertext Mark Up Language used to construct a web
application's front view while CSS was used to make the web page style.
The backend describes the system's data access layer, server and other computer
functions. AJAX and PHP for scripting were used to create the backend of the system.
MYSQL is used for system database development. Server-side software for Apache has
been utilized. In Figure 8, the registration form was developed to provide properly
controlled user details utilizing JavaScript using the Bootstrap Modal function.
LOGIN MODULE
Bootstrap Modal is created with a seemingly smooth and easy to use pop-up display. The
login form is designed. It gives a single connection to the system for physicians and
patients.
BOOKING MODULE
The patient's book appointment menu page shall allow a person to reserve medical
1. XAMPP Server
3. VS Code
4. Chrome Browser
The web base platform with security can be implemented on any micro-computer
3. Core i3 MHz
Any microcomputer of the above capacity is required to be used, the only important thing
is that
i. PHP programming
XAMPP server
3. Install VS Code
9. Name a database
The welcome page module was structured with hypertext markup language, HTML styled
with cascading style sheet, CSS and made dynamic with hypertext pre-processor, PHP.
The link to the login page is included. The Register page is the Link. The details in the
login area are used to assess the page's legitimacy. The log page was constructed in a
cascading styled hypertext markup language and made dynamic with a preprocessor of
hyperlinked text. The centralized system verifies the authenticity of the input code after
inserting a unique patient registration password to verify that the authorized registrar
attempts to access the System; the user will automatically browse the registration system
after it has been validated correctly. The appointment for the patient with physicians is
established on the dashboard where patients can select doctors, wish to be served and
make an appointment. When done, the doctor gets this and immediately begins the
appointment
LOGIN
Admin Credential
Username: admin
Password: Test@12345
Patient Credential
Username: Hulu@gmail.com
Password: ABC321
Doctor Credential
Username: Anujk123@gmail.com
Password: Test @123
Patient Credential
Username: johndoe12@gmail.com
Password: Test@123
CHAPTER FIVE
The evaluation phase of the Hospital Emergency Management System was conducted using
simulated real-world scenarios that closely mirrored actual hospital workflows. Test cases
involved Patients logging into the system to submit emergency requests, detailing their
symptoms, level of urgency, and contact information. These requests were then received by
Doctors through their dedicated dashboards, where they could immediately assess the severity,
acknowledge the case, and provide treatment updates. This simulation allowed for end-to-end
validation of the system’s responsiveness, usability, and data flow integrity across various user
roles.
A particularly innovative component of the system is its automated bid evaluation logic, which
was adapted for healthcare prioritization. Within this context, a "bid" refers to an emergency
request submitted by a patient. The system dynamically ranks these submissions based on
multiple criteria defined by the Admin—primarily urgency level, time of submission, and doctor
availability. This ensures that critical cases receive attention ahead of lower-priority ones,
replicating triage procedures found in emergency departments. PHP scripts were used to generate
comprehensive reports that compiled key metrics, including the number of emergency requests
submitted, response times, doctor activity logs, and outcomes of accepted cases. These reports
provide the Admin with actionable insights and help in strategic planning.
Looking ahead, the system has the potential to evolve into a fully integrated emergency
response platform. Future developments could include real-time ambulance dispatch
coordination, triggered immediately after a high-priority emergency request is submitted. The
integration of SMS and email notification APIs would ensure that patients, doctors, and
emergency personnel receive instant alerts, improving communication and reducing response
times.
Additionally, linking the system with Electronic Health Records (EHRs) would allow doctors
to access a patient's medical history instantly, enabling more informed decision-making.
Integration with wearable health technology such as fitness trackers and smart watches could
provide continuous health monitoring, sending automatic alerts to the system if abnormal vital
signs are detected. This proactive feature would significantly enhance the ability to provide
timely, life-saving interventions and would position the system as a forward-thinking solution in
digital healthcare management.
perform optimally. In poor countries, the outpatients of most clinics encounter many
problems. This includes: extra time during the clinics for doctors and nurses, considerable
wait time for patients and maximum counter-staff workload. Overtime and maximum
workload threatened the quality of the provision of health care. It will design a system to
make the delivery of a web-based appointment system more effective and more quality in
the process of reducing waiting time. This document uses the HTML and CSS for the
Front, Ajax Framework for managing client-Server Requests and Sqlite3 and MYSQL for
its patient and physician by implementing electronic medical records software in general.
In this age of electronic medicine, patients and healthcare practitioners alike have begun
to face new obstacles and are also starting to gain greatly from progress in the field of
health information technology. Only because patients have to overcome time delays will
the scope and extent of use of the hospital appointment system be increased.
Hospital appointment system is a web base programme that plays an important role in the
health sector operations of the hospital. Doctors are scheduled on their illness, or
anything, by patients.
The new system is successfully tested, implemented and complies with all the
requirements given. The system is more secure, versatile, offers more user feedback,
decreases workload, prevents incorrect data entry and offers more functionality than the
current system (manual system). This programme is to promote and encourage the
continuity and improvement of access to medical faculties as soon as feasible not simply
following.
i. The hospital should be networked so that when a patient’s health information
is registered his or her record can be accessed at record office and other
offices.
iii. Lastly, all operators that may likely group to use this system must be
computer literate who have undergone a short training on how to use the
REFERENCES
Akman, D. (2019). “System Analysis and Design Methods 5th Edition. Published by Sandra
Publishers Inc.”
Gerald, V. (2010). Database Management System 2nd Edition. Published by Palmohills prints.
Goldsmith, L. (2012). “History from the inside out: Prison life in nineteenth-century
ies” Inc.
USA.
Ismail, L. (2015) “System Analysis and Design Method 4th Edition. Published by Palgrave
Miley, B. (2016). “Visual Basic 6.0 Progamming Made Easy Published by Palmote Mangrills,”
New York.
<!DOCTYPE HTML>
<html>
<head>
href='http://fonts.googleapis.com/css?family=Ropa+Sans' rel='stylesheet'
type='text/css'>
<script
src="http://ajax.googleapis.com/ajax/libs/jquery/1.8.3/jquery.min.js"></script>
<script src="js/responsiveslides.min.js"></script>
<script>
$(function () {
// Slideshow 1
$("#slider1").responsiveSlides({ maxwidth:
});
});
</script>
</head>
<body>
<!--start-wrap-->
<!--start-header-->
<div class="header">
<div class="wrap">
<!--start-logo-->
<div class="logo">
<!--end-logo-->
<!--start-top-nav-->
<div class="top-nav">
<ul>
<li class="active"><a
href="index.html">Home</a></li>
<li><a href="contact.php">contact</a></li>
</ul>
</div>
<div class="clear"> </div>
<!--end-top-nav-->
</div>
<!--end-header-->
</div>
<!--start-image-slider---->
<div class="image-slider">
</div>
<!--End-image-slider---->
<div class="content-grids">
<div class="wrap">
<img src="images/grid-img3.png">
</div>
<h3>Patients</h3>
class="button"><span><a href="hms/user-
login.php">Click Here</a></span></div>
</div>
</div>
<img src="images/grid-img1.png">
</div>
<div class="text list_1_of_2">
<h3>Doctors Login</h3>
<div class="button"><span><a
href="hms/doctor/">Click Here</a></span></div>
</div>
</div>
<div class="listview_1_of_3 images_1_of_3">
<img src="images/grid-img2.png">
</div>
<h3>Admin Login</h3>
<div class="button"><span><a
href="hms/admin">Click Here</a></span></div>
</div>
</div>
</div>
</div>
</div>
<div class="wrap">
<div class="content-box">
</div>
</div>
</div>
</div>
</div>
<div class="footer">
<div class="wrap">
<div class="footer-left">
<ul>
<li><a href="index.html">Home</a></li>
<li><a href="contact.php">contact</a></li>
</ul>
</div>
</div>
</div>
<!--end-wrap-->
</body>
</html>