Hospital Management

By

Omar Abul Hossain

(12733)
Of

SMART INDIAN SCHOOL, KUWAIT.

A PROJECT REPORT
Submitted to the

FACULTY OF INFOMATICS PRACTICES

In partial fulfillment of the requirements

for the award of the degree

of

GRADE 12
INFORMATICS PRACTICES

CBSE
INDIA

SEPTEMBER, 2024-2025
 BONAFIDE CERTIFICATE

Certified that this project report titled, ‘HOSPITAL MANAGEMENT’ is the

bonafide work of Mr. Omar Abul Hossain who carried out the research under my supervision.

Certified further, that to the best of my knowledge the work reported here in does not form any

other project report or dissertation on the basis of which a degree or award was conferred on an

earlier occasion on this or any other candidate.

Submitted for Viva-Voce examination held at SMART INDIAN SCHOOL, KUWAIT

on …………………...

Internal Examiner External Examiner

 TABLE OF CONTENTS [ T O C ]

SER DESCRIPTION PAGE NO

01 ACKNOWLEDGEMENT 04

02 INTRODUCTION 05

03 OBJECTIVES OF THE PROJECT 05

04 PROPOSED SYSTEM 06

05 SYSTEM DEVELOPMENT LIFE CYCLE (SDLC) 07

06 PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE 08

07 FLOW CHART 16

08 SOURCE CODE 17

09 OUTPUT 22

10 TESTING 24

11 HARDWARE AND SOFTWARE REQUIREMENTS 27

12 BIBLIOGRAPHY 28

3
 ACKNOWLEDGEMENT

The successful completion of my project would

be incomplete without mentioning the names
if those who helped me make this possible. I
take this opportunity to express my gratitude
to all those who helped me with the
completion of this project.
It is my humble pleasure to acknowledge my
Informatics Practices Teacher, Ms. Kartiga G
for her valuablesupport and guidance at each
stage, without which this project would not
have come forth.
I wish to thank my parents for their undivided
support and interest who inspired me and
encouraged me to follow my own intuition and
complete this project.
I also register my sincere gratitude to our
principal, Mr. Mahesh Iyer, for his immense
support.

4
INTRODUCTION

The Hospital Management System (HMS) is designed for Any Hospital to replace
their existing manual, paper-based system. This System targets to provide
complete solution for Hospital and Health care services. This System can be used
in any Hospital, Clinic, Diagnostics or Pathology labs for maintaining patient
details and their test results. It Integrates the entire Resources of a Hospital into
One Integrated Software Application.

OBJECTIVES OF THE PROJECT

The objective of this project is to let the students apply the programming

knowledge into a real- world situation/problem and exposed the students how

programming skills helps in developing a good software.

1. Write programs utilizing modern software tools.

2. Apply object-oriented programming principles effectively when

developing small to medium sized projects.

3. Write effective procedural code to solve small to medium sized problems.

4. Students will demonstrate a breadth of knowledge in computer science, as

exemplified in the areas of systems, theory and software development.

5. Students will demonstrate ability to conduct research or applied Computer

Science project, requiring writing and presentation skills which exemplify

scholarly style in computer science.

5
PROPOSED SYSTEM

Today one cannot afford to rely on the fallible human beings of be really

wants to stand against today’s merciless competition where not to wise saying

“to err is human” no longer valid, it’s outdated to rationalize your mistake. So, to

keep pace with time, to bring about the best result without malfunctioning and

greater efficiency so to replace the unending heaps of flies with a much-

sophisticated hard disk of the computer.

One has to use the data management software. Software has been an

ascent in atomization various organisations. Many software products working

are now in markets, which have helped in making the organizations work easier

and efficiently. Data management initially had to maintain a lot of ledgers and a

lot of paperwork has to be done but now software production this organization

has made their work faster and easier. Now only this software has to be loaded

on the computer and work can be done.

This prevents a lot of time and money. The work becomes fully automated

and any information regarding the organization can be obtained by clicking the

button. Moreover, now it’s an age of computers of and automating such an

organization gives the better look.

6
SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)

The systems development life cycle is a project management technique

that divides complex projects into smaller, more easily managed segments or
phases. Segmenting projects allows managers to verify the successful completion
of project phases before allocating resources to subsequent phases.
Software development projects typically include initiation, planning,
design, development, testing, implementation, and maintenance phases.
However, the phase may be divided differently depending on the organization
involved.
For example, initial project activities might be designated as request,
requirements-definition, and planning phases, or initiation, concept-
development, and planning phases. End users of the system under development
should be involved in reviewing the output of each phase to ensure the system is
being built to deliver the needed functionality.

7
PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE

INITIATION PHASE

The Initiation Phase begins when a business sponsor identifies a need or an

opportunity.

The purpose of the Initiation Phase is to:

Identify and validate an opportunity to improve business

accomplishments of the organization or a deficiency related to a business
need.
Identify significant assumptions and constraints on solutions to that need.
Recommend the exploration of alternative concepts and methods to satisfy
the need including questioning the need for technology, i.e., will a change
in the business process offer a solution?
Assure executive business and executive technical sponsorship. The
Sponsor designates a Project Manager and the business need is
documented in a Concept Proposal. The Concept Proposal includes
information about the business process and the relationship to the
Agency/Organization.
Infrastructure and the Strategic Plan. A successful Concept Proposal
results in a Project Management Charter which outlines the authority of
the project manager to begin
the project.

Careful oversight is required to ensure projects support strategic business

objectives and resources are effectively implemented into an organization's
enterprise architecture. The initiation phase begins when an opportunity to add,
improve, or correct a system is identified and formally requested through the
presentation of a business case. The business case should, at a minimum,
describe a proposal’s purpose, identify expected benefits, and explain how the

8
proposed system supports one of the organization’s business strategies. The
business case should also identify alternative solutions and detail as many
informational, functional, and network requirements as possible.

SYSTEM CONCEPT DEVELOPMENT PHASE

The System Concept Development Phase begins after a business need or

opportunity is validated by the Agency/Organization Program Leadership and
the Agency/Organization CIO.

The purpose of the System Concept Development Phase is to:

Determine the feasibility and appropriateness of the alternatives.

Identify system interfaces.
Identify basic functional and data requirements to satisfy the business
need.
Establish system boundaries; identify goals, objectives, critical success
factors, and performance measures.
Evaluate costs and benefits of alternative approaches to satisfy the basic
functional requirements
Assess project risks
Identify and initiate risk mitigation actions, and develop high-level
technical architecture, process models, data models, and a concept of
operations. This phase explores potential technical solutions within the
context of the business need.
It may include several trade-off decisions such as the decision to use COTS
software products as opposed to developing custom software or reusing
software components, or the decision to use an incremental delivery
versus a complete, onetime deployment.
Construction of executable prototypes is encouraged to evaluate
technology to support the business process. The System Boundary

9
 Document serves as an important reference document to support the
Information Technology Project Request (ITPR) process.
The ITPR must be approved by the State CIO before the project can move
forward.

PICTORIAL REPRESENTATION OF SDLC:

PLANNING PHASE

The planning phase is the most critical step in completing development,

acquisition, and maintenance projects. Careful planning, particularly in the early
stages of a project, is necessary to coordinate activities and manage project risks
effectively. The depth and formality of project plans should be commensurate
with the characteristics and risks of a given project. Project plans refine the
information gathered during the initiation phase by further identifying the
specific activities and resources required to complete a project.
A critical part of a project manager’s job is to coordinate discussions
between user, audit, security, design, development, and network personnel to
identify and document as many functional, security, and network requirements
as possible. During this phase, a plan is developed that documents the approach

10
to be used and includes a discussion of methods, tools, tasks, resources, project
schedules, and user input. Personnel assignments, costs, project schedule, and
target dates are established.
A Project Management Plan is created with components related to
acquisition planning, configuration management planning, quality assurance
planning, concept of operations, system security, verification and validation, and
systems engineering management planning.

REQUIREMENTS ANALYSIS PHASE

This phase formally defines the detailed functional user requirements

using high-level requirements identified in the Initiation, System Concept, and
Planning phases. It also delineates the requirements in terms of data, system
performance, security, and maintainability requirements for the system. The
requirements are defined in this phase to a level of detail sufficient for systems
design to proceed. They need to be measurable, testable, and relate to the
business need or opportunity identified in the Initiation Phase. The requirements
that will be used to determine acceptance of the system are captured in the Test
and Evaluation Masterplan.

The purposes of this phase are to:

Further define and refine the functional and data requirements and
document them in the Requirements Document,
Complete business process reengineering of the functions to be supported
(i.e., verify what information drives the business process, what
information is generated, who generates it, where does the information go,
and who processes it),
Develop detailed data and process models (system inputs, outputs, and the
process.
Develop the test and evaluation requirements that will be used to
determine acceptable system performance.

11
DESIGN PHASE

The design phase involves converting the informational, functional, and

network requirements identified during the initiation and planning phases into
unified design specifications that developers use to script programs during the
development phase. Program designs are constructed in various ways. Using a
top-down approach, designers first identify and link major program components
and interfaces, then expand design layouts as they identify and link smaller
subsystems and connections. Using a bottom-up approach, designers first
identify and link minor program components and interfaces, then expand design
layouts as they identify and link larger systems and connections. Contemporary
design techniques often use prototyping tools that build mock-up designs of
items such as application screens, database layouts, and system architectures.
End users, designers, developers, database managers, and network
administrators should review and refine the prototyped designs in an iterative
process until they agree on an acceptable design. Audit, security, and quality
assurance personnel should be involved in the review and approval process.
During this phase, the system is designed to satisfy the functional requirements
identified in the previous phase. Since problems in the design phase could be
very expensive to solve in the later stage of the software development, a variety
of elements are considered in the design to mitigate risk. These include:

Identifying potential risks and defining mitigating design features.

Performing a security risk assessment.
Developing a conversion plan to migrate current data to the new system.
Determining the operating environment.
Defining major subsystems and their inputs and outputs.
Allocating processes to resources.

12
 Preparing detailed logic specifications for each software module. The
result is a draft System Design Document which captures the preliminary
design for the system.
Everything requiring user input or approval is documented and reviewed
by the user. Once these documents have been approved by the Agency CIO
and Business Sponsor, the final System Design Document is created to
serve as the Critical/Detailed Design for the system.
This document receives a rigorous review by Agency technical and
functional representatives to ensure that it satisfies the business
requirements. Concurrent with the development of the system design, the
Agency Project Manager begins development of the Implementation Plan,
Operations and Maintenance Manual, and the Training Plan.

DEVELOPMENT PHASE

The development phase involves converting design specifications into

executable programs. Effective development standards include requirements
that programmers and other project participants discuss design specifications
before programming begins. The procedures help ensure programmers
clearly understand program designs and functional requirements.
Programmers use various techniques to develop computer programs. The
large transaction-oriented programs associated with financial institutions
have traditionally been developed using procedural programming techniques.
Procedural programming involves the line-by-line scripting of logical
instructions that are combined to form a program. Effective completion of the
previous stages is a key factor in the success of the Development phase. The
Development phase consists of:

Translating the detailed requirements and design into system components.

Testing individual elements (units) for usability.
Preparing for integration and testing of the IT system.

13
INTEGRATION AND TEST PHASE

Subsystem integration, system, security, and user acceptance testing is

conducted during the integration and test phase. The user, with those
responsible for quality assurance, validates that the functional
requirements, as defined in the functional requirements document, are
satisfied by the developed or modified system. OIT Security staff assess the
system security and issue a security certification and accreditation prior to
installation/implementation.

Multiple levels of testing are performed, including:

Testing at the development facility by the contractor and possibly

supported by end users

Testing as a deployed system with end users working together with

contract personnel

Operational testing by the end user alone performing all functions.

Requirements are traced throughout testing; a final Independent
Verification & Validation evaluation is performed and all documentation is
reviewed and accepted prior to acceptance of the system.

IMPLEMENTATION PHASE

This phase is initiated after the system has been tested and accepted by
the user. In this phase, the system is installed to support the intended business
functions. System performance is compared to performance objectives
established during the planning phase. Implementation includes user
notification, user training, installation of hardware, installation of software onto

14
production computers, and integration of the system into daily work processes.
This phase continues until the system is operating in production in accordance
with the defined user requirements.

OPERATIONS AND MAINTENANCE PHASE

The system operation is ongoing. The system is monitored for continued

performance in accordance with user requirements and needed system
modifications are incorporated. Operations continue as long as the system can be
effectively adapted to respond to the organization’s needs. When modifications
or changes are identified, the system may renter the planning phase.

The purpose of this phase is to:

Operate, maintain, and enhance the system.

Certify that the system can process sensitive information.
Conduct periodic assessments of the system to ensure the functional
requirements continue to be satisfied.
Determine when the system needs to be modernized, replaced, or retired.

15
 FLOW CHART

PYTHON-MYSQL CONNECTING

SOFTWARE LOGIN WITH USERNAME&PASSWORD

ASKS USER TO ENTER HIS CHOICE

YOUR NEED WILL BE FULFILLED PYTHON BY

INTERACTING WITH MYSQL

i.e registering-stored in database

getting information-get from database

AGAIN, FIRST PAGE WILL BE OPENED TO FULFILL THE

NEED OF USER

16
 SOURCE CODE
from sys import exit

import mysql.connector as sql

conn=sql.connect(host='localhost',user='root',passwd='',databa

se='project')

if conn.is_connected():

print('successfully connected')

c1=conn.cursor()

print('---------------------------------------------')

print("HOSPITAL MANAGEMENT SYSTEM")

print('---------------------------------------------')

print('"GOD WISHES YOU"')

print("1.LOGIN")

print("2.EXIT")

choice=int(input("ENTER YOUR CHOICE:"))

if choice==1:

u1=input("enter user name:")

pwd1=input("enter the password:")

while u1=='vasu'and pwd1=='vasu6072':

print('connected')

print("WELCOME TO HOSPITAL")

print("successfully connected")

print('1.RegisteringPatient details')

print('2.RegisteringDoctor details')

print('3.RegisteringWorker details')

17
 print("4.total patient details")

print("5.total doctor details")

print("6.total worker details")

print('7.Patient detail')

print('8.Doctor detail')

print('9.Worker detail')

print('10.Exit')

choice=int(input('ENTER YOUR CHOICE:'))

if choice==1:

p_name=input('Enter Patient Name:')

p_age=int(input('Enter Age:'))

p_problems=input('Enter the Problem/Disease:')

p_phono=int(input('Enter Phone number:'))

sql_insert="insert into patient_details

values(""'"+p_name+"',"+str(p_age)+",'"+p_problems+"',"+str(p_

phono)+")"

c1.execute(sql_insert)

print('SUCCESSFULLY REGISTERED')

conn.commit()

elif choice==2:

d_name=input('Enter Doctor Name:')

d_age=int(input('Enter Age:'))

d_department=input('Enter the Department:')

d_phono=int(input('Enter Phone number:'))

18
 sql_insert="insert into doctor_details

values(""'"+d_name+"',"+str(d_age)+",'"+d_department+"',"+str(

d_phono)+")"

c1.execute(sql_insert)

print('successfully registered')

conn.commit()

elif choice==3:

w_name=input('Enter Worker Name:')

w_age=int(input('Enter Age:'))

w_workname=input('Enter type of work:')

w_phono=int(input('Enter Phone number:'))

sql_insert="insert into worker_details

values(""'"+w_name+"',"+str(w_age)+",'"+w_workname+"',"+str(w_

phono)+")"

c1.execute(sql_insert)

print('successfully registered')

conn.commit()

elif choice==4:

sql_w='select*from patient_details '

c1.execute(sql_w)

r = c1.fetchall()

for i in r :

print(i)

19
 elif choice==5:

sql_x="select*from doctor_details"

c1.execute(sql_x)

s=c1.fetchall()

for i in s:

print(i)

elif choice==6:

sql_y="select*from worker_details"

c1.execute(sql_y)

t=c1.fetchall()

for i in t:

print(i)

elif choice==7:

h=input("Enter the name:")

sql_w='select*from patient_details where

p_name=("{}")'.format(h)

c1.execute(sql_w)

u = c1.fetchall()

for i in u:

print(i)

elif choice==8:

d=input("Enter the name:")

20
 sql_d='select*from doctor_details where

p_name=("{}")'.format(d)

c1.execute(sql_d)

v=c1.fetchall()

for i in v:

print(i)

elif choice==9:

f=input("Enter the name:")

sql_f='select*from worker_details where

p_name=("{}")'.format(f)

c1.execute(sql_f)

w=c1.fetchall()

for i in w:

print(i)

elif choice==10:

exit()

break

else:

print('wrong username&password')

if choice==2:

exit()

21
OUTPUT

Login output:

After login:

22
After choosing choice:

23
TESTING

Software Testing is an empirical investigation conducted to provide

stakeholders with information about the quality of the product or service under
test[1] , with respect to the context in which it is intended to operate. Software
Testing also provides an objective, independent view of the software to allow the
business to appreciate and understand the risks at implementation of the
software. Test techniques include, but are not limited to, the process of executing
a program or application with the intent of finding software bugs.
It can also be stated as the process of validating and verifying that a
software program/application/product meets the business and technical
requirements that guided its design and development, so that it works as
expected and can be implemented with the same characteristics. Software
Testing, depending on the testing method employed, can be implemented at any
time in the development process, however the most test effort is employed after the
requirements have been defined and coding process has been completed.

TESTING METHODS
Software testing methods are traditionally divided into black box testing
and white box testing. These two approaches are used to describe the point of
view that a test engineer takes when designing test cases.

BLACK BOX TESTING

Black box testing treats the software as a "black box," without any
knowledge of internal implementation. Black box testing methods include:
equivalence partitioning, boundary value analysis, all-pairs testing, fuzz testing,
model-based testing, traceability matrix, exploratory testing and specification-
based testing.

SPECIFICATION-BASED TESTING

24
 Specification-based testing aims to test the functionality of software
according to the applicable requirements.[16] Thus, the tester inputs data into,
and only sees the output from, the test object. This level of testing usually
requires thorough test cases to be provided to the tester, who then can simply
verify that for a given input, the output value (or behaviour), either "is" or "is
not" the same as the expected value specified in the test case. Specification-based
testing is necessary, but it is insufficient to guard against certain risks
ADVANTAGES AND DISADVANTAGES

The black box tester has no "bonds" with the code, and a tester's
perception is very simple: a code must have bugs. Using the principle, "Ask and
you shall receive," black box testers find bugs where programmers don't. But, on
the other hand, black box testing has been said to be "like a walk in a dark
labyrinth without a flashlight," because the tester doesn't know how the software
being tested was actually constructed.
That's why there are situations when (1) a black box tester writes many
test cases to check something that can be tested by only one test case, and/or (2)
some parts of the back end are not tested at all. Therefore, black box testing has
the advantage of "an unaffiliated opinion," on the one hand, and the disadvantage
of "blind exploring," on the other.

WHITE BOX TESTING

White box testing, by contrast to black box testing, is when the tester has
access to the internal data structures and algorithms (and the code that
implement these)

Types of white box testing: -

The following types of white box testing exist:
ape testing - Testing of the application using Public and Private
APIs.

25
 Code coverage - creating tests to satisfy some criteria of code
coverage.
For example, the test designer can create tests to cause all statements in
the program to be executed at least once.
fault injection methods.
mutation testing methods.
static testing - White box testing includes all static testing.

CODE COMPLETENESS EVALUATION

White box testing methods can also be used to evaluate the completeness
of a test suite that was created with black box testing methods. This allows the
software team to examine parts of a system that are rarely tested and ensures
that the most important function points have been tested.

Two common forms of code coverage are:

Function Coverage: Which reports on functions executed and
Statement Coverage: Which reports on the number of lines executed
to complete the test.
They both return coverage metric, measured as a percentage

26
 HARDWARE AND SOFTWARE REQUIREMENTS

I.OPERATING SYSTEM : WINDOWS 10 AND ABOVE

II. PROCESSOR : PENTIUM(ANY) OR AMD

ATHALON (3800+- 4200+ DUALCORE)

III. MOTHERBOARD : 1.845 OR 915,995 FOR PENTIUM 0R MSI

K9MM-V VIAK8M800+8237R PLUS

CHIPSET FOR AMD ATHALON

IV. RAM : 512MB+

V. Hard disk : SATA 40 GB OR ABOVE

VI. CD/DVD r/w multi drive combo: (If back up required)

VII. FLOPPY DRIVE 1.44 MB : (If Backup required)

VIII. MONITOR 14.1 or 15 -17 inch

IX. Key board and mouse

X. Printer : (if print is required – [Hard copy])

SOFTWARE REQUIREMENTS:

I. Windows OS
II. Python

27
 BIBLIOGRAPHY

1. Info With Python - Class XI By : Sumita Arora

2. A Project Report On Blood Bank Management System (BBMS)
By : Praveen M Jig jinni
3. Website: https://www.w3resource.com

***

28