Scribd
Upload
736 views3 pages

Case Study 1

The document describes a case study to design a database for a multi-specialty hospital. The database would include tables to store information about hospital departments, doctors, patients, rooms, and track patients as they are checked in, receive treatment, are admitted, undergo operations, and are discharged. Constraints are defined for each table to ensure data integrity.

Uploaded by

Murtaza
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
736 views3 pages

Case Study 1

The document describes a case study to design a database for a multi-specialty hospital. The database would include tables to store information about hospital departments, doctors, patients, rooms, and track patients as they are checked in, receive treatment, are admitted, undergo operations, and are discharged. Constraints are defined for each table to ensure data integrity.

Uploaded by

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

Case Study 1

Hospital Management System

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 information stored in this table includes department name, department
location, and facilities available in that department.

Constraint: Department name will be unique for each department.

2.      ALL_DOCTORS: This table stores information about all the doctors working for the
hospital and the departments they are associated with. Each doctor is given an identity
number starting 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, qualification, 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


additional doctors are required. Doctors are referred to by their doctor number. Other
personal details like name, qualification, 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 patient arrives in the
hospital for a check up. When patient arrives, a patient 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. After
storing the necessary details patient 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 patients who get treatment from
the doctor referred to. Details like patient number from patient entry table, doctor number,
date of check up, diagnosis, and treatment are stored. One more field status is used to
indicate whether patient is admitted, referred for operation or is a regular patient to the
hospital. If patient is admitted, 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 patient is admitted, his/her related details are stored in this table.
Information stored includes patient number, advance payment, mode of payment, room
number, department, date of admission, initial condition, diagnosis, treatment, number of
the doctor under whom treatment is done, attendant 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 patient gets discharged from the
hospital. Each entry includes details like patient 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 patients are stored in this table. Information 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 patient is operated in the hospital, his/her details are stored in this table.
Information stored includes patient number, date of admission, date of operation, number of
the doctor who conducted the operation, number of the operation theater in which operation
was carried out, type of operation, patient’s condition before and after operation, 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 patient number, patient 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

You might also like