Patient and Database Systems Guidelines

Only available on StudyMode
  • Download(s) : 1184
  • Published : February 23, 2013
Open Document
Text Preview
EE4791 Database Systems
Guidelines* for Tutorial 1
* Disclaimer: These are guidelines, rather than the actual solutions.

1. For each of the following pairs of entities indicate whether (under typical university circumstances) there is a one-to-many or a many-to-many relationship. Then using the shorthand notation introduced in the lecture, draw a diagram for each of the relationships.

a. STUDENT and COURSE (students register for courses)
Many-to-many (M:N)
STUDENT

COURSE

b. BOOK and BOOK COPY (books have copies)
One-to-many (1:N)
BOOK

BOOK COPY

c. COURSE and TUTORIAL (courses have tutorial sessions)
One-to-many (1:N)
COURSE

TUTORIAL

d. TUTORIAL and ROOM (tutorial sessions are scheduled in rooms) One-to-many (1:N)
ROOM

TUTORIAL

e. INSTRUCTOR and COURSE
Many-to-many (M:N)
INSTRUCTOR

COURSE

Guidelines

p.1

EE4791 Database Systems
Guidelines* for Tutorial 1
* Disclaimer: These are guidelines, rather than the actual solutions.

2. Using the shorthand notation, draw a single diagram to represent the following situation. A BANK has one or more BRANCHes (a BRANCH always belongs to exactly one BANK). Each BRANCH may have one or more CUSTOMERs (but a CUSTOMER is assigned to only one BRANCH). Each CUSTOMER may own one or more ACCOUNTs, but each ACCOUNT is owned by only one

CUSTOMER. Also each CUSTOMER may submit one or more
TRANSACTIONs (but each TRANSACTION is submitted by only one
CUSTOMER). Finally, each ACCOUNT may have many TRANSACTIONs, and a TRANSACTION may be for more than one ACCOUNT.

BANK

BRANCH

ACCOUNT

CUSTOMER

TRANSACTION

Guidelines

p.2

EE4791 Database Systems
Guidelines* for Tutorial 1
* Disclaimer: These are guidelines, rather than the actual solutions.

3. Study the case of the Mountain View Community Hospital (see attached sheets). Then do the following exercises:
a. Case Question 5
Unstructured data:
• Medical scans (MRI, X-Ray, ECG, EEG, Ultrasound, etc)
• Scanned documents (original admission forms filled out by patients, handwritten physician referrals, etc.)
Object-oriented databases are good with unstructured data.
Case Question 6
The PATIENT and PATIENT CHARGES tables are linked by the
Patient_Number attribute, which is common to both tables.
For example, patient 4238 has had three separate charges at the present time.

Guidelines

p.3

EE4791 Database Systems
Guidelines* for Tutorial 1
* Disclaimer: These are guidelines, rather than the actual solutions.

b. Case Exercise 1
PATIENT

PATIENT CHARGES

Case Exercise 2
Meta data:
Name
Patient Last
Name
Patient First
Name
Patient Number
Patient Address
Item Description
Item Code
Amount

Type
Character

Length
30

Character

30

Integer
Character
Character
Integer
Decimal

4
40
20
3
7

Min

Max

0

9999

0
0.0

999
99,999.99

Guidelines

Description
Patient’s last
name
Patient’s
first name
Patient ID
Street/City
Item name
Item ID
Amount
Charged

p.4

EE4791 Database Systems
Guidelines* for Tutorial 1
* Disclaimer: These are guidelines, rather than the actual solutions.

Case Exercise 3
Patient Name:
Patient Number:
Patient Address:
Item Code
200
275
700

Dolan, Mark
4238
818 River Run
Item Description
Rome Semi Priv
Radiology
EEG Test

Amount
1600
150
200

Case Exercise 4
E-R diagram for the hospital:
HOSPITAL

PHYSICIAN

CHARGE

PATIENT

WARD

EMPLOYEE

Guidelines

p.5

tracking img