0% found this document useful (0 votes)
25 views45 pages

Aswin Cs Proj FR

Uploaded by

gigac6260
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
25 views45 pages

Aswin Cs Proj FR

Uploaded by

gigac6260
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 45

Computer Science

HOSPITAL
Management System
COMPUTER SCIENCE

Avani.SS
Name: Aswin 2023-2024
Batch: 2024-2025

Class: XII Reg. No:

Polymers in Aerospace | 1
This is certified to be the bonafide Computer Science project
of Mr ASWIN S, Roll Number ________________________,
Admission Number 2175, Class XII, Division A, of this school
during the academic year 2024-25, as prescribed by the
Central Board of Secondary Education.

Date: Teacher-In-Charge
( Computer Science Department )

Examiner Principal
TABLE OF CONTENTS

Sl.N DESCRIPTION

01 ACKNOWLEDGEMENT

02 INTRODUCTION

03 OBJECTIVES OF THE PROJECT

04 PROPOSED SYSTEM

05 SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)

06 PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE

07 TESTING

08 HARDWARE AND SOFTWARE REQUIREMENTS

09 SOURCE CODE

10 OUTPUT

11 CONCLUSION

12 BIBLIOGRAPHY
I am grateful to Almighty for giving me the strength to
successfully conduct my experiment and for sustaining
my efforts which many a time did oscillate.

It would be my utmost pleasure to express my sincere


thanks to my PGT Computer Science Arjun Sir in
providing a helping hand in this project. Her valuable
guidance, support and supervision all through this
project are responsible for attaining its present form.

I am obliged to our Principal Mrs.Rajashree Mam for


providing the best facilities and environment to bring
out my innovation and spirit of inquiry through this
venture.

I am grateful to my parents whose blessings and wishes


have gone a long way in the completion of this task.

Last but not the least I thank all my friends and


batchmates, without their prompt support my efforts
would be in vain.
PROJECT ON

HOSPITAL MANAGEMENT SYSTEM

Introduction
The Scope of the project takes care of the details of each and every department. These
details gives the doctor, staffs, specialists and patient details including their salary,
Attendance, doctor’s appointments and the billing system. The details of Doctor and
staff help the hospital to maintain the record of every person. Their attendance details
help them to know about their attentive presence while salary is calculated. The billing
system provides an efficient way for calculating bill details of the patients.

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 expose the students to 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 demonstrate a breadth of knowledge in computer science, as exemplified
in the areas of systems, theory and software development. Students demonstrate
ability to conduct research or applied Computer Science project, requiring writing
and presentation skills which exemplify scholarly style in computer science.

PROPOSED SYSTEM
The wise saying “To err is human” is no longer valid, it’s out-dated to rationalize your
mistake. One cannot afford to rely on fallible human beings if one really wants to
withstand today’s merciless competition. So, to keep pace with time, to bring about the
best result without malfunctioning and for greater efficiency we can replace the heaps of
files with a more sophisticated hard disk of the computer .
One has to use the data management software. Software has been an asset in automation
of various organisations. Many software products available now in markets, have helped
in making the organization’s work easier and efficient. Data management initially had to
maintain a lot of ledgers and a lot of paperwork. But now, software has helped this
organization make their work faster and easier. Now, only this software has to be loaded
on the computer and the work can be done.
This prevents a loss of time and money. 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 and automating such an organization gives it a better look.
PLANNING ANALYSIS DESIGN

IMPLEMENTATION

SUPPORT
construction,testing

& software
(consisted of three iterations on
differernt hardware platforms)

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 phases
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.
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 proposed system supports one of the organization’s
business strategies.

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 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.

The SDLC can be an obstacle to development if it's not implemented with care. For
example, if the requirements of customers and other stakeholders aren't considered, the
system's requirements may not be understood from the start.
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 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 Master Plan.
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.

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.
• 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.

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 assesses 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 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 on-going. 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 re-enter 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.

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

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)
The following types of white box testing exist:
• Api testing - Testing of the application using Public and Private APIs.
• 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.

HARDWARE AND SOFTWARE REQUIREMENTS

HARDWARE REQUIREMENTS :

I. OPERATING SYSTEM : WINDOWS 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 multidrive combo: ( if backup 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
III. MySQL
SOURCE CODE
while(True):

print("""

================================

WELCOME TO MYHOSPITAL

================================

""")

import mysql.connector

passwd=str(input("ENTER THE DATABASE PASSWORD;"))

mysql=mysql.connector.connect(host="localhost",user="root",password="Leon@123")

mycursor=mysql.cursor()

mycursor.execute("create database if not exists my_hospitals")

mycursor.execute("use my_hospitals")

mycursor.execute("create table if not exists patient_details(puid int(10) primary


key,name varchar(30) not null,sex char(2),age int(3),address varchar(50),contact int)")

mycursor.execute("create table if not exists doctor_details(name varchar(30) primary


key,specialisation varchar(40),age int(2),address varchar(30),contact varchar(15),fees
int(10),monthly_salary int(10))")

mycursor.execute("create table if not exists nurse_details(name varchar(30) primary


key,age int(2),address varchar(30),contact varchar(15),monthly_salary int(10))")
mycursor.execute("create table if not exists other_workers_details(name varchar(30)
primary key,age int(2),address varchar(30),contact varchar(15),monthly_salary int(10))")

mycursor.execute("create table if not exists user_data(username varchar(30) primary


key,password varchar(30) default'000')")

while(True):

print("""

1. SIGN IN (LOGIN)

2. SIGN UP (REGISTER)

""")

r=int(input("enter your choice:"))

if r==2:

print("""

=======================================

!!!!!!!PLEASE REGISTER YOURSELF!!!!!!!!

=======================================

""")

u=input("ENTER YOUR PREFERRED USERNAME!!:")

p=input("ENTER YOUR PREFERRED PASSWORD (PASSWORD SHOULD BE


STRONG!!!:")
mycursor.execute("insert into user_data values('"+u+"','"+p+"')")

mysql.commit()

print("""

=======================================

!!!!!!!!REGISTERED SUCCESSFULLY!!!!!!!!

=======================================

""")

x=input("enter any key to continue:")

elif r==1:

print("""

==================================

!!!!!!!! {{SIGN IN }} !!!!!!!!!!

==================================

""")

un=input("ENTER THE USERNAME!!:")


ps=input("ENTER THE PASSWORD!!:")

mycursor.execute("select password from user_data where username='"+un+"'")

row=mycursor.fetchall()

for i in row:

a=list(i)

if a[0]==str(ps):

while(True):

print("""

1.ADMINISTRATION

2.PATIENT (ADMISSION NAD DISCHARGE PROCESS)

3.SIGN OUT

""")

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

if a==1:
print("""

1. SHOW DETAILS

2. ADD NEW MEMBER

3. DELETE EXISTING ONE

4. EXIT

""")

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

if b==1:

print("""

1. DOCTOR DETAILS

2. NURSE DETAILS

3. OTHER WORKERS

""")

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

if c==1:

mycursor.execute("select * from doctor_details")

row=mycursor.fetchall()

for i in row:
b=0

v=list(i)

k=["NAME","SPECIALISATION","AGE","ADDRESS","CONTACT","FEES","MONTHLY_SALARY
"]

d=dict(zip(k,v))

print(d)

elif c==2:

mycursor.execute("select * from nurse_details")

row=mycursor.fetchall()

for i in row:

v=list(i)

k=["NAME","SPECIALISATION","AGE","ADDRESS","CONTACT","MONTHLY_SALARY"]

d=dict(zip(k,v))

print(d)

elif c==3:

mycursor.execute("select * from other_workers_details")

row=mycursor.fetchall()

for i in row:
v=list(i)

k=["NAME","SPECIALISATION","AGE","ADDRESS","CONTACT","MONTHLY_SALARY"]

d=dict(zip(k,v))

print(d)

elif b==2:

print("""

1. DOCTOR DETAILS

2. NURSE DETAILS

3. OTHER WORKERS

""")

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

if c==1:

name=input("ENTER DR. NAME:")

spe=input("ENTER SPECIALISATION:")

age=input("ENTER AGE:")

add=input("ENTER ADDRESS:")
cont=input("ENTER CONTACT NO.:")

fees=input("ENTER FEES:")

ms=input("ENTER MONTHLY_SALARY:")

mycursor.execute("insert into doctor_details


values('"+name+"','"+spe+"','"+age+"','"+add+"','"+cont+"','"+fees+"','"+ms+"')")

mysql.commit()

print("SUCCESSFULLY ADDED")

elif c==2:

name=input("ENTER NURSE NAME:")

age=input("ENTER AGE:")

add=input("ENTER ADDRESS:")

cont=input("ENTER CONTACT NO.:")

ms=int(input("ENTER MONTHLY_SALARY:"))

mycursor.execute("insert into nurse_details


values('"+name+"','"+age+"','"+add+"','"+cont+"','"+str(ms)+"')")

mysql.commit()

print("SUCCESSFULLY ADDED")
elif c==3:

name=input("ENTER WORKER NAME:")

age=input("ENTER AGE:")

add=input("ENTER ADDRESS:")

cont=input("ENTER CONTACT NO.:")

ms=input("ENTER MONTHLY_SALARY:")

mycursor.execute("insert into other_workers_details


values('"+name+"','"+age+"','"+add+"','"+cont+"','"+ms+"')")

mysql.commit()

print("SUCCESSFULLY ADDED")

elif b==3:

print("""

1. DOCTOR DETAILS

2. NURSE DETAILS

3. OTHER WORKERS

""")

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

if c==1:
name=input("ENTER DOCTOR'S NAME:")

mycursor.execute("select * from doctor_details where


name=='"+name+"'")

row=mycursor.fetchall()

print(row)

p=input("you really wanna delete this data? (y/n):")

if p=="y":

mycursor.execute("delete from doctor_details where


name='"+name+"'")

mysql.commit()

print("SUCCESSFULLY DELETED!!")

else:

print("NOT DELETED")

elif c==2:

name=input("ENTER NURSE NAME:")

mycursor.execute("select * nurse_details where name=='"+name+"'")

row=mycursor.fetchall()

print(row)

p=input("you really wanna delete this data? (y/n):")

if p=="y":
mycursor.execute("delete from nurse_details where
name='"+name+"'")

mysql.commit()

print("SUCCESSFULLY DELETED!!")

else:

print("NOT DELETED")

elif c==3:

name=input("ENTER THE WORKER NAME:")

mycursor.execute("select * from workers_details where


name=='"+name+"'")

row=mycursor.fetchall()

print(row)

p=input("you really wanna delete this data? (y/n):")

if p=="y":

mycursor.execute("delete from other_workers_details where


name='"+name+"'")

mysql.commit()

print("SUCCESSFULLY DELETED!!")

else:

print("NOT DELETED")

elif b==4:
break

elif a==2:

print("""

1. SHOW PATIENT DETAILS

2. ADD NEW PATIENT

3. DISCHARGE PATIENT

4. EXIT

""")

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

if b==1:

mycursor.execute("select * from patient_details")

row=mycursor.fetchall()

for i in row:

b=0

v=list(i)

k=["NAME","SEX","AGE","ADDRESS","CONTACT"]

d=dict(zip(k,v))

print(d)

elif b==2:
puid=str(input("ENTER patientid : "))

name=str(input("ENTER NAME: "))

sex=str(input("ENTER SEX: "))

age=str(input("ENTER AGE: "))

address=str(input("ADDRESS: "))

contact=str(input("CONTACT NUMBER: "))

mycursor.execute ("insert into patient_details


values('"+str(puid)+"','"+str(name)+"','"+str(sex)+"','"+str(age)+"','"+str(address)+"','"+str(co
ntact)+"')")

mysql.commit()

mycursor.execute("select * from patient_details")

for i in mycursor:

v=list(i)

k=['puid','NAME','AGE','ADDRESS','CONTACT']

print(dict(zip(k,v)))

print("""

====================================

!!!!!!!REGISTERED SUCCESSFULLY!!!!!!

====================================

""")
elif b==3:

name=input(“ENTER THE PATIENT NAME:”)

mycursor.execute(“select * from patient_details where


name='"+name+"'")

row=mycursor.fetchall()

print(row)

bill=input(“HAS HE PAYED ALL THE BILLS?? (y/n):")

if bill=="y":

mycursor.execute("delete from patient_details where


name='"+name+"'")

mysql.commit()

elif b==4:

break

elif a==3:

break

else:

break

mysql.close()
OUTPUT
CONCLUSION

We are very delighted and relieved with the successful completion of our
project. We have made a small attempt at developing a computer-based solution
for Hospital Management System. This project helped us immensely in
understanding the basic principles behind the operations involved within
Python-MySQL project environment. This has also enabled us to learn deeply in
Python Pandas, Matplotlib and PiPy Community.

We tested the Hospital Management System and were found to be working


satisfactorily and no serious errors are spotted. Hence this software project has
been developed to fulfill the academic learning in CBSE Class XII, computer
science curriculum.
BIBLOGRAPHY

1. Computer science With Python - Class XI/XII By : Sumita Arora


2. A Project Report On Blood Bank Management System (BBMS) By : Praveen M
Jigajinni
3. Website: https://python4csip.com/

***

You might also like