Group Ac vity

Slot: B11+B12+B13

DBMS Ac vity- 6

Members: Sonakshi Saxena 23BAI10191

Arya Poovaiah Machamada 23BAI10077

Rishit Aggarwal 23BAI10329
Sanjivni Katiyar 23BAI10287
Samarth Sanjay Jadhav 23BAI10454
Shivam Panday 23BAI10608
Siya Zanwar 23BAI10582
Deepali Mittal 23BAI10645
Jay Kamavisdar 23BAI11391
Bhawna chaurasia 23BAI10924
Hospital Management System

Aim: XYZ hospital is a multi specialty hospital that includes a number of departments, rooms,
doctors, nurses, compounders, and other staff working in the hospital. Patients having different
kinds of ailments come to the hospital and get checkup done from the concerned doctors. If
required they are admitted in the hospital and discharged after treatment.

The aim of this case study is to design and develop a database for the hospital to maintain the
records of various departments, rooms, and doctors in the hospital. It also maintains records of
the regular patients, patients admitted in the hospital, the check up of patients done by the
doctors, the patients that have been operated, and patients discharged from the hospital.

Description: In hospital, there are many departments like Orthopedic, Pathology,

Emergency, Dental, Gynecology, Anesthetics, I.C.U., Blood Bank, Operation Theater, Laboratory,
M.R.I., Neurology, Cardiology, Cancer Department, Corpse, etc. There is an OPD where patients
come and get a card (that is, entry card of the patient) for check up from the concerned doctor.
After making entry in the card, they go to the concerned doctor’s room and the doctor checks
up their ailments. According to the ailments, the doctor either prescribes medicine or admits
the patient in the concerned department. The patient may choose either private or general room
according to his/her need. But before getting admission in the hospital, the patient has to fulfill
certain formalities of the hospital like room charges, etc. After the treatment is completed, the
doctor discharges the patient. Before discharging from the hospital, the patient again has to
complete certain formalities of the hospital like balance charges, test charges, operation charges
(if any), blood charges, doctors’ charges, etc.

Next we talk about the doctors of the hospital. There are two types of the doctors in the hospital,
namely, regular doctors and call on doctors. Regular doctors are those doctors who come to the
hospital daily. Calls on doctors are those doctors who are called by the hospital if the concerned
doctor is not available.

Table Description:
Following are the tables along with constraints used in Hospital Management database.
1. DEPARTMENT: This table consists of details about the various departments in the hospital.
The informa on stored in this table includes department name, department loca on, and
facili es available in that department.

Constraint: Department name will be unique for each department.

2. ALL_DOCTORS: This table stores informa on about all the doctors working for the hospital
and the departments they are associated with. Each doctor is given an iden ty number
star ng with DR or DC prefixes only.

Constraint: Identity number is unique for each doctor and the corresponding
department should exist in DEPARTMENT table.

3. DOC_REG: This table stores details of regular doctors working in the hospital. Doctors are
referred to by their doctor number. This table also stores personal details of doctors like
name, qualifica on, address, phone number, salary, date of joining, etc.

Constraint: Doctor’s number entered should contain DR only as a prefix and must exist
in ALL_DOCTORS table.

4. DOC_ON_CALL: This table stores details of doctors called by hospital when addi onal
doctors are required. Doctors are referred to by their doctor number. Other personal
details like name, qualifica on, fees per call, payment due, address, phone number, etc.,
are also stored.

Constraint: Doctor’s number entered should contain DC only as a prefix and must exist
in ALL_DOCTORS table.

5. PAT_ENTRY: The record in this table is created when any pa ent arrives in the hospital for
a check up. When pa ent arrives, a pa ent number is generated which acts as a primary
key. Other details like name, age, sex, address, city, phone number, entry date, name of
the doctor referred to, diagnosis, and department name are also stored. A er storing the
necessary details pa ent is sent to the doctor for check up.

Constraint: Patient number should begin with prefix PT. Sex should be M or F only.
Doctor’s name and department referred must exist.

6. PAT_CHKUP: This table stores the details about the pa ents who get treatment from the
doctor referred to. Details like pa ent number from pa ent entry table, doctor number,
date of check up, diagnosis, and treatment are stored. One more field status is used to
indicate whether pa ent is admi ed, referred for opera on or is a regular pa ent to the
hospital. If pa ent is admi ed, further details are stored in PAT_ADMIT
 table. If patient is referred for operation, the further details are stored in PAT_OPR table
and if patient is a regular patient to the hospital, the further details are stored in PAT_REG
table.

Constraint: Patient number should exist in PAT_ENTRY table and it should be unique.

7. PAT_ADMIT: When pa ent is admi ed, his/her related details are stored in this table.
Informa on stored includes pa ent number, advance payment, mode of payment, room
number, department, date of admission, ini al condi on, diagnosis, treatment, number
of the doctor under whom treatment is done, a endant name, etc.

Constraint: Patient number should exist in PAT_ENTRY table. Department, doctor

number, room number must be valid.

8. PAT_DIS: An entry is made in this table whenever a pa ent gets discharged from the
hospital. Each entry includes details like pa ent number, treatment given, treatment
advice, payment made, mode of payment, date of discharge, etc.

Constraint: Patient number should exist in PAT_ENTRY table.

9. PAT_REG: Details of regular pa ents are stored in this table. Informa on stored includes
date of visit, diagnosis, treatment, medicine recommended, status of treatment, etc.

Constraint: Patient number should exist in patient entry table. There can be multiple
entries of one patient as patient might be visiting hospital repeatedly for check up and
there will be entry for patient’s each visit.

10. PAT_OPR: If pa ent is operated in the hospital, his/her details are stored in this table.
Informa on stored includes pa ent number, date of admission, date of opera on, number
of the doctor who conducted the opera on, number of the opera on theater in which
opera on was carried out, type of opera on, pa ent’s condi on before and a er
opera on, treatment advice, etc.

Constraint: Patient number should exist in PAT_ENTRY table. Department, doctor

number should exist or should be valid.

11. ROOM_DETAILS: It contains details of all rooms in the hospital. The details stored in this
table include room number, room type (general or private), status (whether occupied or
not), if occupied, then pa ent number, pa ent name, charges per day, etc.

Constraint: Room number should be unique. Room type can only be G or P and status
can only be Y or N
E-R Diagram

Rela onal Database Schema for Case Study

The rela onal database schema for Hospital Management database is as follows:

1. DEPARTMENT (D_NAME, D_LOCATION, FACILITIES)

2. ALL_DOCTORS (DOC_NO, DEPARTMENT)

3. DOC_REG(DOC_NO, D_NAME, QUALIFICATION, SALARY, EN_TIME, EX_TIME, ADDRESS,

PH_NO, DOJ)
4. DOC_ON_CALL (DOC_NO, D_NAME, QUALIFICATION,
FS_PR_CL, PYMT_DU, ADDRESS, PH_NO)

5. PAT_ENTRY (PAT_NO, PAT_NAME, CHKUP_DT, PT_AGE,

SEX, RFRG_CSTNT, DIAGNOSIS, RFD, ADDRESS, CITY,
PH_NO, DEPARTMENT)

6. PAT_CHKUP (PAT_NO, DOC_NO, DIAGNOSIS, STATUS, TREATMENT)

7. PAT_ADMIT (PAT_NO, ADV_PYMT, MODE_PYMT,

ROOM_NO, DEPTNAME, ADMTD_ON, COND_ON,
INVSTGTN_DN, TRMT_SDT, ATTDNT_NM)

8. PAT_DIS (PAT_NO, TR_ADVS, TR_GVN, MEDICINES, PYMT_GV, DIS_ON)

9. PAT_REG (PAT_NO, DATE_VIS, CONDITION, TREATMENT, MEDICINES,

DOC_NO, PAYMT)

10. PAT_OPR (PAT_NO, DATE_OPR, IN_COND,

AFOP_COND, TY_OPERATION, MEDICINES, DOC_NO,
OPTH_NO, OTHER_SUG)

11. ROOM_DETAILS (ROOM_NO, TYPE, STATUS, RM_DL_CRG, OTHER_CRG)