0% found this document useful (0 votes)
89 views5 pages

Database Initial Study

The ER diagram models the entities Patient, Physician, Nurse, Ward, Treatment, and Prescription. A Physician treats many Patients and a Patient can be treated by many Physicians. A Nurse services a Ward and a Ward is serviced by many Nurses. A Treatment has a Prescription and a Patient receives a Treatment.

Uploaded by

Aina
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
0% found this document useful (0 votes)
89 views5 pages

Database Initial Study

The ER diagram models the entities Patient, Physician, Nurse, Ward, Treatment, and Prescription. A Physician treats many Patients and a Patient can be treated by many Physicians. A Nurse services a Ward and a Ward is serviced by many Nurses. A Treatment has a Prescription and a Patient receives a Treatment.

Uploaded by

Aina
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/ 5

DATABASE

INITIAL STUDY

DATABASE
DESIGN

IMPLEMENTATION
AND LOADING

TESTING AND
EVALUATION

OPERATION

MAINTENANCE
AND EVOLUTION
QUESTION 2
You are assigned to design a Hospital Management System for Klang Valley Medical Center. The
following are requirements of the system:

There are three types of employee in this hospital which are physician (medical doctor), nurse and
administration. Unlike administration staff, a physician and a nurse staff has special attributes. A
physician has a qualification and expert area. A nurse staff has position and ward_id where she is
placed
A physician treats many patients and a patient can be treated by more than one physician
Each treatment has prescription. The prescription has a prescription_id, date, product code, dosage
and amount.
A patient can be placed in a ward
A ward is serviced by several nurse staffs. The ward information has ward number, building, ward
type and number of beds.

Based on the above information, create a complete ER diagram that shows all entities, relationships,
attributes and connectivity (by using Crow’s Foot). Prepare the relational schema for the diagram
developed.
Information about a flight includes its unique flight number, its origin, destination and estimated
departure and arrival times. To reduce costs, the MalBol operation only has nonstop with a single
origin and destination.
Flights are scheduled for one or more dates with an airplane and a crew assigned to each flight.
(This means that the same flight number may be scheduled on different dates using different
airplanes and a different set of crewmembers). In a crew assignment, the employee number and the
role (eg. Captain, flight attendant) are noted.

Airplanes have a unique serial number, a model, a capacity and next-scheduled-maintenance date
The maintenance record of an airplane includes a unique maintenance number, a date, a
description, the serial number of the plane and the employee responsible for the repairs.
Employees have a unique employee number, a name, a phone and a job title.
Customer has a unique customer number, a phone number and a name
A record is maintained of flight reservations including a unique reservation number, a flight number,
a customer number, a date, a fare and a payment method (cash or credit card). If the payment is by
credit card, a credit card number and an expiry date of the card are also recorded.
EMPLOYEE
PK emp_id
emp_name

OV
H
G
PHYSICIAN NURSE
C
II PK,FK1 emp_id
H
PK,FK1 emp_id
qualification position
G
expert_area
C
I< FK2 ward_id

H
gives O services

WARD
TREATMENT
I< PK,FK1 emp_id
II PK ward_id
ward_num
I< PK,FK2 patient_id
ward_building
FK3 presc_id
II ward_type
receives ward_no_of_bed
has

PATIENT
PRESCRIPTION
II PK patient_id
II PK presc_id
patient_name
presc_date
presc_code
dosage
amount
EMPLOYEE MAINTENANCE
PK emp_num PK main_num
emp_name main_date
emp_phone main_desc
emp_job_title FK1 ap_serial
FK2 emp_num

CREW AIRPLANE
PK crew_assign PK ap_serial
FK emp_num ap_model
crew_role ap_capacity
ap_nsm_date

FLIGHT
PK flight_num
flight_origin CUSTOMER
flight_dest PK cust_num
flight_est_depart cust_name
flight_arr_time cust_phone
ap_serial
crew_assign

RESERVATION
PK res_num
FK1 flight_num
FK2 cust_num
res_date
res_fare
res_pay_method
credit_card_num
exp_card

You might also like