Hospital Management System

ABSTRACT
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 (on forms) 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.

A significant part of the operation of any hospital involves the acquisition, management and
timely retrieval of great volumes of information. This information typically involves; patient personal
information and medical history, staff information, room and ward scheduling, staff scheduling,
operating theater scheduling and various facilities waiting lists. All of this information must be
managed in an efficient and cost wise fashion so that an institution's resources may be effectively
utilized HMS will automate the management of the hospital making it more efficient and error free. It
aims at standardizing data, consolidating data ensuring data integrity and reducing inconsistencies.

Shanthiniketan College of Science and Management Studies, BCA

1
 Hospital Management System

INTRODUCTION

Shanthiniketan College of Science and Management Studies, BCA

2
 Hospital Management System

CHAPTER 1

INTRODUCTION
The Hospital Management System (HMS) is designed for Any Hospital to replace their existing manual,
paper based system. The new system is to control the following information; patient information, room
availability, staff and operating room schedules, and patient invoices. These services are to be provided
in an efficient, cost effective manner, with the goal of reducing the time and resources currently required
for such tasks.

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 (on forms) 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.

A significant part of the operation of any hospital involves the acquisition, management and
timely retrieval of great volumes of information. This information typically involves; patient personal
information and medical history, staff information, room and ward scheduling, staff scheduling, operating
theater scheduling and various facilities waiting lists. All of this information must be managed in an
efficient and cost wise fashion so that an institution's resources may be effectively utilized HMS will
automate the management of the hospital making it more efficient and error free. It aims at standardizing
data, consolidating data ensuring data integrity and reducing inconsistencies.

Shanthiniketan College of Science and Management Studies, BCA

3
 Hospital Management System

1.1 Goals of project:

Enhanced Patient Care: The core objective is to improve the patient experience. This involves
automating tasks (appointment scheduling, billing) and streamlining workflows to reduce wait
times and improve communication between patients and staff.
Cost Reduction: Streamlining operations through the HMS can significantly reduce hospital
operating costs. This can be achieved through better resource management (staffing,
equipment), optimized inventory control (medical supplies, pharmaceuticals), and improved
billing efficiency.
Data-Driven Decisions: An effective HMS provides a Management Information System (MIS).
This offers real-time reports and analytics to management, enabling informed decision-making
about resource allocation, staffing levels, and overall hospital strategy.
Improved Department Coordination: Effective communication and collaboration between
departments are crucial for smooth hospital operations. The HMS can facilitate this by
providing a central platform for information sharing and streamlined workflows across
departments like admissions, pharmacy, and radiology.
Centralized Control: The HMS offers a single platform for top management to oversee all
hospital operations. This allows them to monitor key metrics, identify areas for improvement,
and ensure all departments are aligned with overall goals.

1.2 Objectives:

Streamline Operations: Develop a Hospital Management System (HMS) to improve efficiency

in patient care, staff scheduling, and resource allocation.
Enhance Patient Care: Facilitate faster check-in, reduced wait times, and improved
communication through features like appointment scheduling and Electronic Health Records
(EHR).
Boost Revenue and Decision Making: Increase billing accuracy, generate reports for better
resource management, and optimize workflows for a healthier bottom line.

Shanthiniketan College of Science and Management Studies, BCA

4
 Hospital Management System

1.3 Project overview

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 (on forms) 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.
.

1.4 Scope:

The Hospital Management System (HMS) is designed for Any Hospital to replace their existing
manual, paper based system. The new system is to control the following information; patient information,
room availability, staff and operating room schedules, and patient invoices. These services are to be
provided in an efficient, cost effective manner, with the goal of reducing the time and resources currently
required for such tasks.
A significant part of the operation of any hospital involves the acquisition, management and
timely retrieval of great volumes of information. This information typically involves; patient personal
information and medical history, staff information, room and ward scheduling, staff scheduling, operating
theater scheduling and various facilities waiting lists. All of this information must be managed in an
efficient and cost wise fashion so that an institution's resources may be effectively utilized HMS will
automate the management of the hospital making it more efficient and error free. It aims at standardizing
data, consolidating data ensuring data integrity and reducing inconsistencies.
.
Reception:

The reception module handles various enquiries about the patient's admission and discharge details, bed
census, and the patient's movements within the hospital. The system can also handle fixed-cost package
deals for patients as well as Doctor Consultation and Scheduling, Doctor Consultancy Fees and Time
Allocation.
Doctor visit schedule

Shanthiniketan College of Science and Management Studies, BCA

5
 Hospital Management System

Doctor Appointment Scheduling

Enquiry of Patient
Find History of Patient Enquired.

Administration:
This module handles all the master entry details for the hospital requirement such as consultation detail,
doctor specialization, consultancy fee, and service charges.
Employee
Employee Detail Recording.
Doctor Type .
Doctor Master
Referral Doctor

Pharmacy:

This module deals with all medical items. This module helps in maintaining Item Master, Receipt of
Drugs/consumables, issue, handling of material return, generating retail bills, stock maintenance. It also
helps in fulfilling the requirements of both IPD and OPD Pharmacy.

Laboratory:
This module enables the maintenance of investigation requests by the patient and generation of test
results for the various available services, such as clinical pathology, X-ray and ultrasound tests.
Requests can be made from various points, including wards, billing, sample collection and the laboratory
receiving point. The laboratory module is integrated with the in-patient/ outpatient registration, wards
and billing modules.

Shanthiniketan College of Science and Management Studies, BCA

6
 Hospital Management System

Registration:

This module helps in registering information about patients and handling both IPD and OPD
patient’s query. A unique ID is generated for each patient after registration. This helps in
implementing customer relationship management and also maintains medical history of the
patient.

1.5 Purpose:

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 (on forms) 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.

A significant part of the operation of any hospital involves the acquisition, management
and timely retrieval of great volumes of information. This information typically
involves; patient personal information and medical history, staff information, room and
ward scheduling, staff scheduling, operating theater scheduling and various facilities
waiting lists. All of this information must be managed in an efficient and cost wise
fashion so that an institution's

Shanthiniketan College of Science and Management Studies, BCA

7
 Hospital Management System

1.6 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 (on forms) 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.

1.7 Proposed system:

The Hospital Management System (HMS) is designed for Any Hospital to replace their existing
manual, paper based system. The new system is to control the following information; patient information,
room availability, staff and operating room schedules, and patient invoices. These services are to be
provided in an efficient, cost effective manner, with the goal of reducing the time and resources currently
required for such tasks.

Shanthiniketan College of Science and Management Studies, BCA

8
 Hospital Management System

1.8 Project modules

Reception:

The reception module handles various enquiries about the patient's admission and discharge details, bed
census, and the patient's movements within the hospital. The system can also handle fixed-cost package
deals for patients as well as Doctor Consultation and Scheduling, Doctor Consultancy Fees and Time
Allocation.
Doctor visit schedule
Doctor Appointment Scheduling
Enquiry of Patient
Find History of Patient Enquired.

Administration:
This module handles all the master entry details for the hospital requirement such as consultation detail,
doctor specialization, consultancy fee, and service charges.
Employee
Employee Detail Recording.
Doctor Type .
Doctor Master

Pharmacy:

module deals with all medical items. This module helps in maintaining Item Master, Receipt of
Drugs/consumables, issue, handling of material return, generating retail bills, stock
maintenance. It also helps in fulfilling the requirements of both IPD and OPD Pharmacy

This module helps in registering information about patients and handling both IPD and OPD
patient’s query. A unique ID is generated for each patient after registration.

Shanthiniketan College of Science and Management Studies, BCA

9
 Hospital Management System

SOFTWARE
REQUIREMENT ANALYSIS

Shanthiniketan College of Science and Management Studies, BCA

10
 Hospital Management System

CHAPTER 2
SOFTWARE REQUIREMENT ANALYSIS

2.1 Software requirements:

Any Version of browser after Mozilla Firefox 4.0, Internet Explorer 6.0,chrome

2.2 Hardware requirements:

a. Any processor after Pentium 4.

b. Any version of Windows XP or later.

c.Processor speed: 2.0 GHz

d. RAM : 1GB

e. Hard disk: 40GB to 80 GB

2.3 Software requirements:

a. Database : MySQL

b. Server : Apache

c. Frontend : HTML

d. Scripting Language : JavaScript

e. IDE : Sublime

f.Technology : PHP

Shanthiniketan College of Science and Management Studies, BCA

11
 Hospital Management System

2.4 Software’s used

2.4.1 Frontentend technology used:

Hospital management systems rely heavily on front-end technologies to deliver user-friendly

interfaces and efficient workflows. Frameworks like React and Angular, powered by
JavaScript, ensure real-time updates and seamless interactions for features like appointment
scheduling and medical record viewing. HTML5 provides the foundational structure, while
CSS3 allows for clear and visually appealing design that prioritizes accessibility for all
users. Data visualization libraries come into play by presenting complex medical data, such
as patient trends and resource allocation, in a clear and understandable way using charts and
graphs. This powerful combination empowers healthcare professionals to streamline daily
tasks, improve patient care, and optimize resource utilization, leading to a more positive
experience for everyone involved.

Performance:

Performance in Hospital management systems is crucial for ensuring efficiency and

effectiveness in managing records. Front-end technologies are employed to optimize user
interfaces for fast loading times and responsive interactions. Techniques such as lazy loading
of images and components help minimize initial load times, while asynchronous data fetching
ensures that updates and real-time analytics are promptly displayed. Utilizing lightweight
frameworks and libraries, coupled with efficient code practices, further enhances the system's
responsiveness and usability across different devices and network conditions.

Shanthiniketan College of Science and Management Studies, BCA

12
 Hospital Management System

Portability:

A critical feature for modern hospital management systems is portability. This refers to the
ability to seamlessly transfer patient data between different systems. This is vital for
ensuring continuity of care. When patients switch hospitals or clinics, their medical history
needs to follow them. Portable data allows new providers to access crucial information for
informed decisions, ultimately improving patient care. Additionally, portability eliminates
the need for time-consuming and error-prone manual data entry between systems. This
streamlines workflows and frees up valuable time for healthcare professionals to focus on
patients. Finally, portability empowers patients themselves. They can manage their own
health information, easily share it with different providers, or access it through a personal
health record system. This fosters a more collaborative approach to healthcare. Standardized
data formats, secure APIs for communication between systems, and patient-controlled
access mechanisms are all key aspects of achieving portability. By prioritizing portability,
hospital management systems can contribute to a more interconnected healthcare ecosystem,
benefiting patients, providers, and the overall efficiency of the healthcare landscape.

Open source:

Open-source hospital management systems offer an attractive alternative to traditional

options. They're budget-friendly, eliminating licensing fees, and highly customizable to fit
specific hospital needs. This control is often limited with proprietary systems. Open-source
also boasts stronger security due to publicly viewable code, allowing the community to
quickly address vulnerabilities. Plus, a vibrant community provides ongoing support and
potential feature enhancements. However, there are downsides. Setting up and maintaining
an open-source system might require additional technical expertise or paid support. Open-
source options may also have fewer features than some commercial counterparts, although
customization can help mitigate this. Finally, while transparency is a plus, robust security
measures are crucial for protecting sensitive patient data. Overall, open-source hospital
management systems are a viable option for cost-conscious hospitals seeking customization
and transparency, but careful consideration of potential drawbacks and internal resources is
essential.
.

Shanthiniketan College of Science and Management Studies, BCA

13
 Hospital Management System

2.4.2 Third Party Application Support:

Hospital management systems (HMS) can significantly benefit from third-party application
support. This integration allows the HMS to connect with specialized software and
services, extending its functionality beyond core tasks like scheduling and billing. Imagine
the HMS seamlessly interacting with applications for:

 Advanced Analytics: Third-party tools can analyze patient data to identify trends, predict
resource needs, and optimize staffing.
 Telemedicine Integration: Integrating telemedicine platforms allows for remote
consultations, improving patient access to care and reducing hospital visits.
 Patient Engagement Apps: These apps can empower patients to manage appointments,
access medical records, and communicate with doctors, streamlining communication and care
coordination.

2.4.3 PHP Server:

A PHP server can serve as the foundation for a robust hospital management system (HMS).
PHP excels at handling web requests and interacting with databases, making it ideal for
building a dynamic and user-friendly interface. This translates to features like:

 Secure Login System: The PHP server can manage user accounts for doctors,
administrators, and potentially even patients, ensuring controlled access to sensitive
information.
 Patient Management: Patients can register online, schedule appointments, and view
medical records (with proper access controls). Doctors can access patient data, update
charts, and prescribe medications – all facilitated by the PHP server.
 Appointment Booking and Scheduling: The system can manage appointment scheduling,
send reminders, and integrate with calendars for seamless coordination.

Shanthiniketan College of Science and Management Studies, BCA

14
 Hospital Management System

DESIGN

Shanthiniketan College of Science and Management Studies, BCA

15
 Hospital Management System

CHAPTER 3
DESIGN PHASE

3.1 INTRODUCTION

 Design precedes development: It's the foundation for building any software system. Just like
designing a blueprint for a house, software design defines the structure and functionalities
before coding begins.
 Three key activities: While coding, implementation, and testing are crucial, design is
paramount. It sets the groundwork for a successful and maintainable software product.
 Decisions made during design impact the final product: These decisions influence the
software's reliability, maintainability, and overall quality.
 Translating requirements: Design bridges the gap between what the customer needs and the
final software. It takes the gathered requirements and translates them into a concrete plan for
building the software.
 Two-step process: Software design is often a two-step process. The first step, preliminary
design, focuses on transforming requirements into a data-driven representation.
In essence, a well-designed software system is more likely to be:
 Reliable: It functions consistently and as intended.
 Maintainable: Easy to modify, fix, and update as requirements evolve.
 High-quality: Meets the customer's needs and delivers a positive user experience.
By emphasizing design upfront, software development teams can build robust and successful software
solutions.

Shanthiniketan College of Science and Management Studies, BCA

16
 Hospital Management System

3.2 UML Diagrams:

a. The unified modelling language allows the software engineer to express an analysis model
using the modelling notation that is governed by a set of syntactic semantic and pragmatic rules.

b.A UML system is represented using five different views that describe the system from
distinctly different perspective. Each view is defined by a set of diagram, which is as follows.

User Model View

a. This view represents the system from the users perspective.

b.The analysis representation describes a usage scenario from the end-users perspective.
Structural model view

a. In this model the data and functionality are arrived from inside the system.

b.This model view models the static structures.

Behavioural Model View

It represents the dynamic of behavioural as parts of the system, depicting the interactions of
collection between various structural elements described in the user model and structural model
view.

Implementation Model View

In this the structural and behavioural as parts of the system are represented as they are to be
built.

Environmental Model View

In this the structural and behavioural aspects of the environment in which the system is to be
implemented are represented.

UML is specifically constructed through two different domains they are

a. UML Analysis modelling, which focuses on the user model and structural model views of the
system?

b. UML design modelling, which focuses on the behavioural modelling, implementation

modelling and environmental model views.

Shanthiniketan College of Science and Management Studies, BCA

17
 Hospital Management System

3.3 Use case diagrams:

Registration

Reception

Discharge Summary
Patient
Doctor

Laboratory

Pharmacy

Shanthiniketan College of Science and Management Studies, BCA

18
 Hospital Management System

3.4 SEQUENCE DIAGRAM:

Sequence diagram and collaboration diagram are called INTERACTION DIAGRAMS. An interaction
diagram shows an interaction, consisting of set of objects and their relationship including the messages that may
be dispatched among them.
A sequence diagram is an introduction that empathizes the time ordering of messages. Graphically a
sequence diagram is a table that shows objects arranged along the X-axis and messages ordered in increasing time
along the Y-axis

Patient Discharge
Doctor Resgistration Reception Laboratory Pharmacy Summary

login

View appointments

Register

Send request

done any surgeries

Go to Laboratory

Take madicine

send discharge summary

Discharge patient

Shanthiniketan College of Science and Management Studies, BCA

19
 Hospital Management System

3.5 Activity Diagram

start

Doctor Patient

Registration

Pharmacy

Reception

Discharge
Laboratory summary

End

Shanthiniketan College of Science and Management Studies, BCA

20
 Hospital Management System

3.6 Database Design:

ADO.NET and accessing the database through applets and ADO.NET API via an intermediate
server resulted server resulted in a new type of database model which is different from the client-server
model. Based on number of intermediate server through the request should go it is named as single tire,
two tire and multi tire architecture

Single Tier

In a single tier the server and client are the same in the sense that a client program that needs information
(client) and the source of this type of architecture is also possible in java, in case flat files are used to store the data.
However this is useful only in case of small applications. The advantage with this is the simplicity and portability
of the application developed.

Server and
client

Database

Shanthiniketan College of Science and Management Studies, BCA

21
 Hospital Management System

Two Tier (client-server)

In two tier architecture the database resides in one machine and client in different machine they are
connected through the network. In this type of architecture a database management takes control of the
database and provides access to clients in a network. This software bundle is also called as the server.
Software in different machines, requesting for information are called as the clients.

Server

Client
Database

Client

Shanthiniketan College of Science and Management Studies, BCA

22
 Hospital Management System

TBLcontact table Structure : This table store the detail of contact Doctor Registration

Name NULL / NOTNULL TYPE KEY

Name Null Varchar (20)
Loginid Null Varchar(20)
password Null Varchar(20)
Department Null Varchar(20)
Specialization Null Varchar(20)
Phonenumber Null Bigint
Address Null Varchar(20)
Email Null Varchar(20)

Employee Registration

Name NULL / NOTNULL TYPE KEY

Name Null Varchar (20)
Loginid Null Varchar(20)
password Null Varchar(20)
Department Null Varchar(20)
Phonenumber Null Bigint
Address Null Varchar(20)
Email Null Varchar(20)

Inpatient Registration

Name NULL / NOTNULL TYPE KEY

Patientname Null Varchar (20)
Patientid Not Null Varchar(20) Primary
Gender Null Varchar(20)
Age Null Int
Phoneres Null Bigint
Phonemob Null Bigint
Maritual Null Varchar(20)
Occupation Null Varchar(20)
Admid Null Int
Admdate Null Datetime
Admtime Null Datetime
Status Null Varchar(20)
Symptoms Null Varchar(20)
Department Null Varchar(20)
Wardno Null Int
Bedno Null Int
Doctor Null Varchar(20)

Shanthiniketan College of Science and Management Studies, BCA

23
 Hospital Management System

Out Patient Registration

Name NULL / NOTNULL TYPE KEY

Patientname Null Varchar (20)
Patientid Not Null Varchar(20) Primary
Gender Null Varchar(20)
Age Null Int
Address Null Varchar(20)
Assigndoctor Null Varchar(20)
Phoneres Null Bigint
Phonemob Null Bigint
Opdate Null Datetime
Department Null Varchar(20)

For Patient Information

Name NULL / NOTNULL TYPE KEY

Pid Not null Varchar(20) Foreign
Patientname Null Varchar(20)
Age Null Int
Department Null Varchar(20)
Doctor Null Varchar(20)

For Surgery Information

Name NULL / NOTNULL TYPE KEY

Pid Not null Varchar(20) Foreign
Patientname Null Varchar(20)
Age Null Int
Department Null Varchar(20)
Doctor Null Varchar(20)
Surgerydate Null Datetime

Shanthiniketan College of Science and Management Studies, BCA

24
 Hospital Management System

For Blood test

Name NULL / NOTNULL TYPE KEY

Patienttype Null Varchar(20)
Patientid Null Varchar(20)
Patientname Null Varchar(20)
Mediclatestype Null Varchar(20)
Bloodgroup Null Varchar(20)
Haemoglobin Null Varchar(20)
Bloodsugar Null Varchar(20)
Sacid Null Varchar(20)
Description Null Varchar(20)

For Urine test

Name NULL / NOTNULL TYPE KEY

Patienttype Null Varchar(20)
Patientid Null Varchar(20)
Department Null Varchar(20)
Patientname Null Varchar(20)
Medicine Null Varchar(20)

For Discharge Summary

Name NULL / NOTNULL TYPE KEY

Patientid Null Varchar(20)
Patientname Null Varchar(20)
Joiondate Null Datetime

Shanthiniketan College of Science and Management Studies, BCA

25
 Hospital Management System

E-R Diagram:

E-R (Entity-Relationship) Diagram is used to represents the relationship

between entities in the table.

The symbols used in E-R diagrams are:

SYMBOL PURPOSE

Represents Entity sets.

Represent attributes.

Represent Relationship Sets.

Line represents flow

Structured analysis is a set of tools and techniques that the analyst.

To develop a new kind of a system:

The traditional approach focuses on the cost benefit and feasibility analysis,
Project management, and hardware and software selection a personal
considerations.

Shanthiniketan College of Science and Management Studies, BCA

26
 Hospital Management System

ER Diagram of Hospital Management System:

Shanthiniketan College of Science and Management Studies, BCA

27
 Hospital Management System

IMPLEMENTATION

Shanthiniketan College of Science and Management Studies, BCA

28
 Hospital Management System

CHAPTER 4

IMPLEMENTATION

Shanthiniketan College of Science and Management Studies, BCA

29
 Hospital Management System

Shanthiniketan College of Science and Management Studies, BCA

30
 Hospital Management System

Shanthiniketan College of Science and Management Studies, BCA

31
 Hospital Management System

Shanthiniketan College of Science and Management Studies, BCA

32
 Hospital Management System

Shanthiniketan College of Science and Management Studies, BCA

33
 Hospital Management System

Shanthiniketan College of Science and Management Studies, BCA

34
 Hospital Management System

Shanthiniketan College of Science and Management Studies, BCA

35
 Hospital Management System

Shanthiniketan College of Science and Management Studies, BCA

36
 Hospital Management System

TESTING

Shanthiniketan College of Science and Management Studies, BCA

37
 Hospital Management System

CHAPTER 5

TESTING

5.1 Testing:
Testing is a process of executing a program with the indent of finding an error. Testing is
a crucial element of software quality assurance and presents ultimate review of specification, design and
coding.

System Testing is an important phase. Testing represents an interesting anomaly for the software. Thus
a series of testing are performed for the proposed system before the system is ready for user acceptance
testing.

A good test case is one that has a high probability of finding an as undiscovered error. A successful
test is one that uncovers an as undiscovered error.

Testing Objectives:

1. Testing is a process of executing a program with the intent of finding an error

2. A good test case is one that has a probability of finding an as yet undiscovered error
3. A successful test is one that uncovers an undiscovered error

Testing Principles:

 All tests should be traceable to end user requirements

 Tests should be planned long before testing begins
 Testing should begin on a small scale and progress towards testing in large
 Exhaustive testing is not possible
 To be most effective testing should be conducted by a independent third party

The primary objective for test case design is to derive a set of tests that has the highest livelihood for
uncovering defects in software. To accomplish this objective two different categories of test case design
techniques are used. They are

Shanthiniketan College of Science and Management Studies, BCA

38
 Hospital Management System

5.2 White-box testing:

White box testing focus on the program control structure. Test cases are derived to ensure that
all statements in the program have been executed at least once during testing and that all logical
conditions have been executed.

5.3 Block-box testing:

Black box testing is designed to validate functional requirements without regard to the internal workings
of a program. Black box testing mainly focuses on the information domain of the software, deriving test
cases by partitioning input and output in a manner that provides through test coverage. Incorrect and
missing functions, interface errors, errors in data structures, error in functional logic are the errors falling
in this category.

Testing strategies:

A strategy for software testing must accommodate low-level tests that are necessary to verify that
all small source code segment has been correctly implemented as well as high-level tests that validate
major system functions against customer requirements.

Testing fundamentals:

Testing is a process of executing program with the intent of finding error. A good test case is one that has
high probability of finding an undiscovered error. If testing is conducted successfully it uncovers the errors in the
software. Testing cannot show the absence of defects, it can only show that software defects present.

Shanthiniketan College of Science and Management Studies, BCA

39
 Hospital Management System

Testing Information flow:

Information flow for testing flows the pattern. Two class of input provided to test the process.
The software configuration includes a software requirements specification, a design specification and
source code.

Test configuration includes test plan and test cases and test tools. Tests are conducted and all the
results are evaluated. That is test results are compared with expected results. When erroneous data are
uncovered, an error is implied and debugging commences.

5.4 Unit testing:

Unit testing is essential for the verification of the code produced during the coding phase and
hence the goal is to test the internal logic of the modules. Using the detailed design description as a guide,
important paths are tested to uncover errors with in the boundary of the modules. These tests werecarried
out during the programming stage itself. All units of Vienna SQL were successfully tested.

5.5 Integration testing:

Integration testing focuses on unit tested modules and build the program structure that is dictated
by the design phase.

5.6 System testing:

System testing tests the integration of each module in the system. It also tests to find discrepancies
between the system and it’s original objective, current specification and system documentation. The
primary concern is the compatibility of individual modules. Entire system is working properly or not will
be tested here, and specified path ODBC connection will correct or not, and giving output or not are tested
here these verifications and validations are done by giving input values to the system and by comparing
with expected output. Top-down testing implementing here.

Shanthiniketan College of Science and Management Studies, BCA

40
 Hospital Management System

5.7 Acceptance Testing:

This testing is done to verify the readiness of the system for the implementation. Acceptance
testing begins when the system is complete. Its purpose is to provide the end user with the confidence
that the system is ready for use. It involves planning and execution of functional tests, performance tests
and stress tests in order to demonstrate that the implemented system satisfies its requirements.

1. Regression Testing:
o Changes: Test the system after updates, patches, or modifications to ensure existing
functionalities are not affected.
o Automated Tests: Implement automated regression tests to streamline testing efforts and
ensure consistency.
2. Documentation:
o Test Cases: Document test cases, including inputs, expected outputs, and actual results.
o Reports: Provide comprehensive reports summarizing test results, issues found, and
resolutions.
3. Compliance Testing (Optional):
o Regulations: If applicable, ensure the system complies with healthcare industry
regulations (e.g., HIPAA in the US, GDPR in Europe).

Ensure that your report covers each phase of white box testing, detailing methodologies, tools used, test
cases, results, and any recommendations for improvements. This structured approach will help ensure
the reliability, security, and performance of your Hospital Management System.

Shanthiniketan College of Science and Management Studies, BCA

41
 Hospital Management System

Tools to special importance during acceptance testing include:

Test coverage Analyzer – records the control paths followed for each test case.

Timing Analyzer – also called a profiler, reports the time spent in various regions of the code are areas
to concentrate on to improve system performance.

Coding standards – static analyzers and standard checkers are used to inspect code for deviations from
standards and guidelines.

5.8 Test Cases:

Test cases are derived to ensure that all statements in the program have been executed at least
once during testing and that all logical conditions have been executed.
Using White-Box testing methods, the software engineer can drive test cases that
 Guarantee that logical decisions on their true and false sides.
 Exercise all logical decisions on their true and false sides.
 Execute all loops at their boundaries and with in their operational bounds.
 Exercise internal data structure to assure their validity.
The test case specification for system testing has to be submitted for review before system testing
commences.

Shanthiniketan College of Science and Management Studies, BCA

42
 Hospital Management System

Shanthiniketan College of Science and Management Studies, BCA

43
 Hospital Management System

SCREENSHOTS

Shanthiniketan College of Science and Management Studies, BCA

44
 Hospital Management System

CHAPTER 6

SCREENSHOTS

Home Page:

Shanthiniketan College of Science and Management Studies, BCA

45
 Hospital Management System

Dashboard:

Shanthiniketan College of Science and Management Studies, BCA

46
 Hospital Management System

Registration

Shanthiniketan College of Science and Management Studies, BCA

47
 Hospital Management System

Inpatient Registration

Shanthiniketan College of Science and Management Studies, BCA

48
 Hospital Management System

Out patient Registration

Shanthiniketan College of Science and Management Studies, BCA

49
 Hospital Management System

Administration

Shanthiniketan College of Science and Management Studies, BCA

50
 Hospital Management System

Doctors Appointments

Shanthiniketan College of Science and Management Studies, BCA

51
 Hospital Management System

Patient Info

Shanthiniketan College of Science and Management Studies, BCA

52
 Hospital Management System

Patient Reports

Shanthiniketan College of Science and Management Studies, BCA

53
 Hospital Management System

Medical Tests

Shanthiniketan College of Science and Management Studies, BCA

54
 Hospital Management System

Discharge Summary

Shanthiniketan College of Science and Management Studies, BCA

55
 Hospital Management System

Ambulatory Information

Shanthiniketan College of Science and Management Studies, BCA

56
 Hospital Management System

Pharmacy

Shanthiniketan College of Science and Management Studies, BCA

57
 Hospital Management System

CONCLUSION

Shanthiniketan College of Science and Management Studies, BCA

58
 Hospital Management System

CHAPTER 7

CONCLUSION

The well-considered design of this Hospital Management System (HMS) positions it for long-term
success. The emphasis on modularity allows for future modifications, ensuring the system can adapt to
evolving hospital needs. This translates into several immediate benefits. Automation streamlines
processes, boosting overall efficiency. A user-friendly interface improves the experience for staff
compared to the previous system. Security remains a top priority, safeguarding both the system itself and
the sensitive patient data it stores. Role-based access control ensures data security by granting users
appropriate permissions. Communication bottlenecks are eliminated, fostering better collaboration across
departments. Updating information becomes effortless, maintaining accurate and up-to-daterecords. In
essence, this project has delivered a robust, user-friendly, and adaptable HMS that promises to
significantly improve hospital operations and, most importantly, patient care.

Shanthiniketan College of Science and Management Studies, BCA

59
 Hospital Management System

FUTURE ENHANCEMENT

Shanthiniketan College of Science and Management Studies, BCA

60
 Hospital Management System

CHAPTER 8

FUTURE ENHANCEMENT

The future of Hospital Management Systems (HMS) is brimming with exciting possibilities. Data-
driven advancements like Artificial Intelligence and advanced analytics promise to revolutionize patient
care through personalized medicine, predictive health insights, and optimized resource allocation.
Integration with the Internet of Things (IOT) can further enhance patient monitoring with real-time
data from wearable devices and smart equipment. Additionally, interoperable data sharing across
healthcaresystems will create a more holistic view of patient care.
The patient experience can also be significantly improved. Enhanced patient portals can become a one-
stop shop for appointments, medication management, and secure communication with doctors.
Telemedicine integration will expand access to care, especially for remote or mobility-restricted
patients.
Security and privacy will remain paramount. Advanced cybersecurity protocols and potentially even
block chain technology can safeguard sensitive patient data.
Furthermore, hospitals can embrace sustainability initiatives by utilizing the HMS to track and reduce
their environmental footprint. Finally, ongoing staff training and support will ensure optimal adoption
and utilization of this powerful system, paving the way for a future of efficient, data-driven, and patient-
centered healthcare.

Shanthiniketan College of Science and Management Studies, BCA

61
 Hospital Management System

BIBLIOGRAPHY

Shanthiniketan College of Science and Management Studies, BCA

62
 Hospital Management System

CHAPTER 9

BIBLIOGRAPHY

For PHP

a.https://www.w3schools.com/php/default.a

b.https://www.sitepoint.com/php/

c.https://www.php.net/

For MySQL

a.https://www.mysql.com/

b.http://www.mysqltutorial.org

For XAMPP

a.https://www.apachefriends.org/download.html

Shanthiniketan College of Science and Management Studies, BCA

63